Whether you've found an issue with Brackets, the Brackets Registry or the Brackets Shell, here's how to report the problem...
First, check our Troubleshooting page for solutions to common problems.
When filing a new bug, please include:
git rev-parse HEAD)
Bugs can be caused by Brackets extensions you've added. Before you file an issue, use Debug > Reload Without Extensions to see if the problem still occurs without any extensions.
If that fixes the problem, then please file an issue in the extension's repo instead, so it can be addressed by the extension author. See Troubleshooting extension bugs for tips on identifying which extension is causing the problem.
Please first check our feature backlog on Trello to see if it's already there. You can vote on features in the backlog to help us prioritize them.
Feel free to file new feature requests as an issue on GitHub, just like a bug. We tag these issues "move to backlog" and periodically migrate them onto the feature backlog for you.
We review all new issues on a regular basis. Several things typically happen as part of review:
Depending on priority, milestone, and other workload, a developer may or may not begin working on the bug soon.
Some bugs may be closed without fixing - see "Hey! My bug wasn't fixed!" below.
Yeah, what's up with that? There are a number of reasons an issue might get closed without being fixed:
If you disagree with a bug being closed, feel free to post a comment asking for clarification or re-evaluation. The more new/updated info you can provide, the better.
Yes please! But first...
We use labels/tags for a number of purposes:
|Process||fix in progress||Someone has started work on a fix (or the fix is ready but still undergoing code review - not merged yet).|
|fixed but not closed||Fix has been merged. Waiting for the original bug reporter to verify that it's fixed.|
|last reviewed||Last reviewed/triaged bug. See "Bug review" above.|
|move to backlog||Feature/enhancement request rather than a bug. Will be moved to the feature backlog.|
|Priority||high priority||High impact bug many users will hit (e.g. crash/data loss). We aim for zero high-priority bugs before each release.|
|medium priority||At least somewhat severe and a significant number of users will hit.|
|low priority||Low severity (e.g. small cosmetic issue) and/or few users will hit.|
|no priority||We don't plan to spend time fixing the bug - but we would accept a fix if someone offers a pull request.|
|Feature area||F ...||Labels starting with "F" categorize bugs by feature area.|
|Suggestions||starter bug||Recommended for new contributors as a good intro to the Brackets source code.|
|Extension Idea||May be out of scope for Brackets core, but is a great idea for a Brackets extension.|
|External tracking||codemirror||Needs CodeMirror changes.|
|Needs Chromium Embedded Framework or WebKit/Chromium changes.|
|tracking||Specific bug has been filed in external project - waiting on a fix.|
|Architecturally-focused||architecture||Requires significant architectural changes - needs longer discussion.|
|performance||Perceived or measurable performance issue.|
|code cleanup||The fix improves code maintainability without changing Brackets's functionality.|
|async||Bug caused by asynchronous execution / race condition|
|native shell||Needs code changes in brackets-shell, our desktop native wrapper|
Acronyms we use frequently in bug comments: