There are many ways to contribute to the Visual Studio Code Hex Editor project: logging bugs, submitting pull requests, reporting issues, and creating suggestions.
After cloning and building the repo, check out the issues list.
First, fork the VS Code Hex Editor repository so that you can make a pull request. Then, clone your fork locally:
git clone https://github.com/<<<your-github-account>>>/vscode-hexeditor.git
Occasionally you will want to merge changes in the upstream repository (the official code repo) with your fork.
cd vscode-hexeditor
git checkout main
git pull https://github.com/microsoft/vscode-hexeditor.git main
Manage any merge conflicts, commit them, and then push them to your fork.
In order to download necessary tools, clone the repository, and install dependencies through npm, you need network access.
You'll need the following tools:
cd vscode-hexeditor
npm install
After cloning the extension and running npm install execute npm run watch to initiate esbuild's file watcher and then use the debugger in VS Code to execute "Run Extension".
We use eslint for linting our sources. You can run eslint across the sources by calling npm run lint from a terminal or command prompt.
To lint the source as you make changes you can install the eslint extension.
Even if you have push rights on the Microsoft/vscode-hexeditor repository, you should create a personal fork and create feature branches there when you need them. This keeps the main repository clean and your personal workflow cruft out of sight.
Before we can accept a pull request from you, you'll need to sign a Contributor License Agreement (CLA). It is an automated process and you only need to do it once.
To enable us to quickly review and accept your pull requests, always create one pull request per issue and link the issue in the pull request. Never merge multiple requests in one unless they have the same root cause. Be sure to keep code changes as small as possible. Avoid pure formatting changes to code that has not been modified otherwise. Pull requests should contain tests whenever possible.
We're also interested in your feedback for the future of the hex editor. You can submit a suggestion or feature request through the issue tracker. To make this process more effective, we're asking that these include more information to help define them more clearly.
In order to keep the conversation clear and transparent, please limit discussion to English and keep things on topic with the issue. Be considerate to others and try to be courteous and professional at all times.