This page is mainly about modifying core Brackets code. If you're adding a new feature, consider writing an extension instead.
If you're interested in submitting a pull request, review the guidelines for contributing code. Most importantly:
git clone https://github.com/<username>/brackets.git
git submodule update --init
git remote add upstream https://github.com/adobe/brackets.git
(MUST be run in a Command Prompt started with "Run as Administrator")
Now, when you launch the Brackets app it will load your git copy of the source code, rather than the original source code that was distributed with the installer. It will share the same preferences & set of installed extensions that a regular installed build would use.
Making changes is simple:
For more in-depth instructions see "Getting a Copy of the Code" below.
For hacking on the native code or building the app binaries yourself without running an installer, see "Hacking on brackets-shell" below.
git fetch upstream && git merge upstream/master
git submodule syncand
git submodule update --init
git checkout -b <branchname>
git commit -am "Your commit message here"
git push origin <branchname>
Brackets is primarily built in HTML/JS/CSS, but it currently runs as a desktop app inside a thin native app shell called brackets-shell, based on CEF, that lets it access local files. (It doesn't run in the browser yet, but we're hoping to work on an in-browser version soon.)
The HTML/JS/CSS files are installed along with brackets-shell, but you can set up a separate development copy of these files and then load them in brackets-shell instead of the default installed copy. See Running Your Copy of the Code for more details.
For details on working with Brackets's architecture and APIs, see Brackets Development How-Tos.
Whatever you want, of course! Check out the CONTRIBUTING guide for some ideas.
If you're planning to do something other than a small bugfix, please start a discussion on the brackets-dev Google group or the #brackets IRC channel on freenode to get feedback. There might already be some prior thinking on what you're working on, or some reason that it hasn't already been done. We don't want you to do tons of work and then have to rewrite half of it.
First, sign the Brackets Contributor License Agreement (CLA). This is for your protection as well as that of the Brackets project.
Then, just submit changes as pull requests from your own fork of brackets or brackets-shell. The core dev team works in 2.5-week sprints (weird length, but it works for us). We'll try to review small pull requests quickly in the current sprint. Larger submissions may take longer — but discussing them in advance will smooth the process!
Before you submit your pull request, please make sure it's merged with master and fully tested as described in the Pull Request Checklist.
Note: Don't use the GitHub "ZIP" to get a copy of the source. The auto-generated ZIP file will be missing important dependencies.
The first step is to fork the repo on GitHub so you can start making changes in your local repository. For the HTML/JS/CSS code that comprises the bulk of Brackets, you only need to fork the brackets repo. (See "Hacking on brackets-shell" below if you want to work on the native code as well). To fork a repo, simply click the "Fork" button at the top of the page.
Next pull the repositories down to your local machine.
git clone https://github.com/<your username>/brackets.git cd brackets git submodule update --init
Don't skip the last line! Brackets uses submodules for third-party dependencies (like CodeMirror), so it won't work until you run this command to set them up.
You may also need to run
git submodule updatewhen you switch branches or pull from upstream, since submodule changes aren't updated automatically. If you see third-party code showing up as modified in
git status(something like
M src/thirdparty/CodeMirror2), then you need to run this command.
If you're only hacking on HTML/JS/CSS files, you can have the installed Brackets shell run your local copy of the HTML/JS/CSS code (instead of the default installed copy) by running the
tools/setup_for_hacking script. Here's how:
cdto the root of your brackets repo
tools/setup_for_hacking.sh, passing the full pathname to your installed Brackets.app. For example:
cdto the root of your brackets repo
tools\setup_for_hacking.bat, passing the full path of the directory where Brackets.exe is installed. For example:
tools\setup_for_hacking.bat "C:\Program Files (x86)\Brackets"
You can revert back to running the installed version of the Brackets source at any time by running
tools/restore_installed_build.sh (Mac) or
tools\restore_installed_build.bat (Windows) from your Brackets repo.
Once you are set up, Brackets will pick up the latest changes to the code every time it starts — no build step is needed. (The Grunt scripts are used only to generate a final release build).
It's important to keep up to date with the main Brackets repository to make sure your pull requests match the latest Brackets builds. First you'll first need to link your local clone of Brackets to track the main Brackets repository on GitHub. Run this command from the brackets directory:
cd brackets git remote add upstream https://github.com/adobe/brackets.git
Your repo will now have two "remotes":
origin refers to your fork on GitHub, while
upstream refers to the original, official Brackets repo.
If you want to avoid getting branches other than master, you can add the
--track masterargument after
add. However, that will mean that if you need to pull a different branch, you'll need to explicitly fetch it.
Getting the latest changes on the Brackets
master branch is a two-step process. First:
git fetch upstream
This brings down any new commits into your repo, but doesn't actually update any of your branches. Next, update your current local branch:
git merge upstream/master
This merges any changes from the main Brackets repository into whichever branch you currently have checked out locally. (To update multiple local branches, you'll need to
git checkout each one in turn and repeat the merge command).
You may also need to run
git submodule update at this point — if the output of
git fetch said "Fetching submodule" or if
git status shows an unexpected diff in a third-party library.
Rarely, an entire new submodule is added to Brackets. You'll need to run
git submodule update --init when that happens.
You can see a diff before merging with
git difftool ...upstream/master.
For a higher-level overview (with API important changes called out), check the Release notes after each sprint.
If you also forked the brackets-shell repository, repeat the steps above for the brackets-shell repo, then rebuild the shell once you've pulled down updates.
If you did not fork the brackets-shell repo (i.e. you're using the 'setup_for_hacking' step above), you should update your installed build of Brackets each sprint and rerun the 'setup_for_hacking' script. This ensures you're using the latest app binaries.
If you use Brackets to edit Brackets, you can quickly reload the app itself by choosing Debug > Reload Brackets from the in-app menu. You can also debug Brackets using dev tools — but to keep Reload working properly while dev tools are open, be sure to disable caching as instructed in that link.
You can use Debug > Run Tests to run our unit test suite.
If you've found an issue you want to fix or a feature you want to implement, eventually you'll want to submit a pull request back to Brackets upstream. Here's how to organize your changes so they're ready to turn into a pull request.
First, create a new branch off of
master for the change you want to work on. This allows your
master branch to stay in sync with the main Brackets repository — and if your change doesn't work or breaks something, you can always start fresh from your local
git checkout master git branch mynewfeature git checkout mynewfeature
That creates a new branch called
mynewfeature and sets it as your working branch. Any changes you make now will be linked to that branch. While you work on it, you should still keep your branch in sync with Brackets master following the "Getting Updates from the Main Repository" steps above.
Now go ahead and modify some code, make your fix, and be sure that it works in your copy of Brackets. As always, please follow the guidelines for contributing code to ensure your code matches what's expected for Brackets contributions.
Next it's time to commit your changes to your local git repo. Use
git add <filename> to stage any modified files for committing, then use
git commit -m "COMMIT MESSAGE" to commit those files. (Or just use use
git commit -am "COMMIT MESSAGE" to commit all modified files). Be sure to write a thorough commit message that describes the changes you're making and why.
The last step before submitting a pull request is to push those changes to your GitHub account — so far the changes are only stored in your local copy of the Brackets repository. Remember that your GitHub fork of the Brackets repo is called "origin"... so to push your changes use:
git push origin mynewfeature
That command creates a matching branch on your GitHub-hosted repo and copies your branch's commits into it. Now your commits are stored on the GitHub server and not just locally.
This is a good time to review the Pull Request Checklist — make sure your code passes JSLint, doesn't break any unit tests, etc.
Now you're ready to submit a pull request. Go to the GitHub page for your fork of Brackets and choose your branch from the dropdown near the upper left (it says
master by default). Now you're looking at the code for that branch.
Click the Pull Request button in the top right and you'll be brought to a page that describes the pull request. Make sure you're submitting to the
adobe/brackets repository, from the branch you've been working on.
Review the "Commits" and "Files Changed" tabs to make sure you're submitting only the changes you intend. Write a detailed description of what your pull request does, and include links to any relevant bugs ("#1234" is automatically turned into a link — though avoid writing "fixes #1234", since GitHub will auto-close the bug too soon if it sees a string like that). Then click "Send pull request."
Congratulations on submitting your pull request — you're helping make Brackets even better! Read about the pull request review process for what happens next.
During code review, you will probably be asked to make some changes to your code. First, make sure you're working on the correct branch:
git checkout mynewfeature
Then make the necessary code changes. When done, repeat the
git commit and
git push steps from above.
Ta daa! As soon as you've pushed those changes to "origin" (your fork on GitHub), your pull request is automatically updated with the new code. Finally, add a comment to the pull request describing the new changes — this ensures the code reviewer is notified of your update.
For most of your changes to Brackets, you should only need to edit the HTML/JS/CSS code in the brackets repo. You won't need the source for brackets-shell because you can use a pre-built binary from a Brackets installer to run your modified HTML/JS/CSS code (see instructions above).
However, you may want to set up a dev environment for brackets-shell if:
You want to pull the latest from the brackets repo
master and it requires a new brackets-shell build that hasn't been released as a binary yet. (This is uncommon, but it can happen).