diff options
| author | Colby Swandale <colby-swandale@users.noreply.github.com> | 2017-02-16 22:54:06 +1100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-02-16 22:54:06 +1100 |
| commit | efa9d9c9d8c5a06b31c4e6839e4b4c73b4ace14f (patch) | |
| tree | a977961a85c914d7af8dccb98f0c8a99c3d6743d /doc | |
| parent | 96a947b83d9a547994d3b1aa10d6e70be8493367 (diff) | |
| download | bundler-efa9d9c9d8c5a06b31c4e6839e4b4c73b4ace14f.tar.gz | |
PR feedback and revert `a bug` back to `the bug`
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/contributing/BUG_TRIAGE.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/contributing/BUG_TRIAGE.md b/doc/contributing/BUG_TRIAGE.md index d9a84ab7c7..aa535a0f45 100644 --- a/doc/contributing/BUG_TRIAGE.md +++ b/doc/contributing/BUG_TRIAGE.md @@ -1,6 +1,6 @@ # Bug triage -Triaging is the work of processing tickets that have been opened by users. Common tasks include verifying bugs, categorizing tickets, and ensuring there's enough information to reproduce a bug for anyone who wants to try to fix it. +Triaging is the work of processing tickets that have been opened by users. Common tasks include verifying bugs, categorizing tickets, and ensuring there's enough information to reproduce the bug for anyone who wants to try to fix it. We've created an [issues guide](ISSUES.md) to walk users through the process of how to report an issue with the Bundler project. We also have a [troubleshooting guide](../TROUBLESHOOTING.md) to diagnose common problems. @@ -26,7 +26,7 @@ Everyone is welcome and encouraged to fix any open bug, improve an error message 1. Discuss the fix on the existing issue. Coordinating with everyone else saves duplicate work and serves as a great way to get suggestions and ideas if you need any. 2. Base your commits on the correct branch. Bugfixes for 1.x versions of Bundler should be based on the matching 1-x-stable branch. - 3. Review the [pull request guide](../contributing/PULL_REQUESTS.md) + 3. Review the [pull request guide](../contributing/PULL_REQUESTS.md). 4. Commit the code with at least one test covering your changes to a named branch in your fork. 5. Put a line in the [CHANGELOG](../../CHANGELOG.md) summarizing your changes under the next release under the “Bugfixes” heading. 6. Send us a [pull request](https://help.github.com/articles/using-pull-requests) from your bugfix branch. |