-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2da9390
commit 2f8d050
Showing
1 changed file
with
39 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
We welcome contributions to the debricked VS Code extension project! To contribute, follow these steps: | ||
|
||
## Fork the Repository | ||
1. Fork the repository on GitHub. | ||
2. Clone your fork locally: | ||
```sh | ||
git clone https://github.com/your-username/VS-Code-extension.git | ||
cd VS-Code-extension | ||
``` | ||
|
||
## Create a Branch | ||
1. Create a new branch for your feature or bug fix: | ||
```sh | ||
git checkout -b my-feature-branch | ||
``` | ||
|
||
## Make Changes | ||
1. Make your changes in the codebase. | ||
2. Run tests to ensure everything works: | ||
```sh | ||
npm run test | ||
``` | ||
|
||
## Commit and Push | ||
1. Commit your changes with a descriptive message: | ||
```sh | ||
git commit -m "Add new feature X" | ||
``` | ||
|
||
2. Push your branch to GitHub: | ||
```sh | ||
git push origin my-feature-branch | ||
``` | ||
|
||
## Create a Pull Request | ||
1. Create a pull request from your branch to the `main` branch in the original repository. | ||
2. Ensure all checks pass and your code is reviewed. | ||
|
||
For more details, refer to our [Contribution Guidelines](./CONTRIBUTION_GUIDELINES). |