👍🎉 First off, thanks for taking the time to contribute! 🎉👍

When contributing to this project, please first discuss the changes you wish to make via an issue before making changes.

Please note the Code of Conduct document, please follow it in all your interactions with this project.

Unsure where to begin contributing? You can start by looking through the help-wanted issues.

git clone https://github.com/gitkraken/vscode-gitlens.git

Prerequisites

• Git, >= 2.7.2
• NodeJS, >= 16.14.2
• yarn, >= 1.22.19

From a terminal, where you have cloned the repository, execute the following command to install the required dependencies:

yarn

From a terminal, where you have cloned the repository, execute the following command to re-build the project from scratch:

yarn run rebuild

👉 NOTE! This will run a complete rebuild of the project.

Or to just run a quick build, use:

yarn run build

During development you can use a watcher to make builds on changes quick and easy. From a terminal, where you have cloned the repository, execute the following command:

yarn run watch

Or use the provided watch task in VS Code, execute the following from the command palette (be sure there is no > at the start):

task watch

This will first do an initial full build and then watch for file changes, compiling those changes incrementally, enabling a fast, iterative coding experience.

👉 Tip! You can press CMD+SHIFT+B (CTRL+SHIFT+B on Windows, Linux) to start the watch task.

👉 Tip! You don't need to stop and restart the development version of Code after each change. You can just execute Reload Window from the command palette.

This project uses prettier for code formatting. You can run prettier across the code by calling yarn run pretty from a terminal.

To format the code as you make changes you can install the Prettier - Code formatter extension.

Add the following to your User Settings to run prettier:

"editor.formatOnSave": true,

This project uses ESLint for code linting. You can run ESLint across the code by calling yarn run lint from a terminal. Warnings from ESLint show up in the Errors and Warnings quick box and you can navigate to them from inside VS Code.

To lint the code as you make changes you can install the ESLint extension.

To generate a production bundle (without packaging) run the following from a terminal:

yarn run bundle

To generate a VSIX (installation package) run the following from a terminal:

yarn run package

1. Open the vscode-gitlens folder
2. Ensure the required dependencies are installed
3. Choose the Watch & Run launch configuration from the launch dropdown in the Run and Debug viewlet and press F5.

Note: If you see a pop-up with a message similar to "The task cannot be tracked. Make sure to have a problem matcher defined.", you will need to install the TypeScript + Webpack Problem Matchers extension.

1. Open the vscode-gitlens folder
2. Ensure the required dependencies are installed
3. Choose the Watch & Run (web) launch configuration from the launch dropdown in the Run and Debug viewlet and press F5.

See https://code.visualstudio.com/api/extension-guides/web-extensions#test-your-web-extension-in-a-browser-using-vscodetestweb

1. Open the vscode-gitlens folder
2. Ensure the required dependencies are installed
3. Run the build or watch task from the command palette
4. Run the Run (local web) task from the command palette

See https://code.visualstudio.com/api/extension-guides/web-extensions#test-your-web-extension-in-on-vscode.dev

1. Open the vscode-gitlens folder
2. Ensure the required dependencies are installed
3. Run the build or watch task from the command palette
4. Run the Run (vscode.dev) task from the command palette

Please follow all the instructions in the PR template.

This repository contains both OSS-licensed and non-OSS-licensed files. All files in or under any directory named "plus" fall under LICENSE.plus. The remaining files fall under LICENSE, the MIT license.

If a pull request is submitted which contains changes to files in or under any directory named "plus", then you agree that GitKraken and/or its licensors (as applicable) retain all right, title and interest in and to all such modifications and/or patches.

The Change Log is updated manually and an entry should be added for each change. Changes are grouped in lists by added, changed, removed, or fixed.

Entries should be written in future tense:

• Be sure to give yourself much deserved credit by adding your name and user in the entry

Added

• Adds awesome feature — closes #<issue> thanks to PR #<pr> by Your Name (@<your-github-username>)

Changed

• Changes or improves an existing feature — closes #<issue> thanks to PR #<pr> by Your Name (@<your-github-username>)

Fixed

• Fixes #<issue> a bug or regression — thanks to PR #<pr> by Your Name (@<your-github-username>)

If this is your first contribution to GitLens, please give yourself credit by adding yourself to the Contributors section of the README in the following format:

• Your Name ([@<your-github-username>](https://github.com/<your-github-username>)) &mdash; [contributions](https://github.com/gitkraken/vscode-gitlens/commits?author=<your-github-username>)

GitLens version changes are bucketed into two types:

• minor: normal release (new features, enhancements and fixes)
• patch: hotfix release (just fixes)

Note: major version bumps are only considered for more special circumstances.

All recent changes are listed under ## [Unreleased]. This title and corresponding link at the bottom of the page will need to be updated.

The title should be updated to the upcoming version and the release date (YYYY-MM-DD):

<!-- from: -->

## [Unreleased]

<!-- to: -->

## [12.1.0] - 2022-06-14

Stage this file so it will be included with the version commit.

Run yarn version and enter the upcoming version when prompted.

Once the commit is completed, run git push --follow-tags to push the version commit and the newly generated tags.

After the version commit and new tags are pushed to GitHub, the Publish Stable workflow will be triggered, which will automatically package the extension and deploy it to the VS Marketplace. The release notes should be generated during the action, but if not, this can be done manually using the notes from the Change Log.

If the action fails, the VSIX will need to be built locally with yarn package and uploaded manually in the marketplace.

The Publish Pre-release workflow is automatically run every AM unless no new changes have been committed to main.

The Publish Insiders workflow is no longer available and was replaced with the pre-release edition.