From d728702296bd54e8a540dfa57fc144d4e8b02935 Mon Sep 17 00:00:00 2001 From: Josh Johnson Date: Wed, 13 Jan 2016 18:15:57 -0500 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c123838..25ca154 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,6 +2,23 @@ Thanks for helping out! This guide provides some guidelines on coding styles and architecture for this extension. Keep in mind that these are guidelines, not rules. Use your best judgement and feel free to make suggestions! +## Building the Extension +1. Clone the repository locally and run `npm install` from the vscode-xml directory. +2. Run the `build` task in VS Code (`CTRL + SHIFT + B`) or start extension debugging (`F5`), which will run the `build` task for you. + +## Pull Requests +If you would like to work on an unassigned issue, please: + +1. Comment on the issue so others are aware of your intentions. +2. Make a fork of the repository and create a branch named `issue-#`. +3. When finished, create a pull request using the issue branch. + +If you would like to add unsolicited features, please: + +1. Make a fork of the repository and create a branch named `wip-`. +2. Create a pull request using the WIP branch and prefix the name of the PR with "WIP". +3. The pull request will be used as the channel of communication for discussion around the new feature. Once code is complete, the PR will be treated as per normal. + ## Style Guide In short, favor clean, maintainable code over code that "just works".