550
edits
BMO/comment tagging: Difference between revisions
→Highlighting Important Comments: add section on tagging from 3rd party apps using API
(→Automatic Collapsing of Comments: clarifying how comment tags should be used) |
(→Highlighting Important Comments: add section on tagging from 3rd party apps using API) |
||
| Line 44: | Line 44: | ||
* tagging a comment with “'''STR'''” (steps to reproduce) will help the QA team quickly find the information they need to verify the fix | * tagging a comment with “'''STR'''” (steps to reproduce) will help the QA team quickly find the information they need to verify the fix | ||
* writing a comment summarising a new feature and tagging it with “'''docs'''” will help the generation of documentation for MDN or similar | * writing a comment summarising a new feature and tagging it with “'''docs'''” will help the generation of documentation for MDN or similar | ||
==== Comment Tagging from Apps ==== | |||
Applications using our APIs can post tags to comments. | |||
===== Bugherder ===== | |||
The [https://bugherder.mozilla.org/ bugherder application] will post a comment on behalf of a user when they take an action: | |||
* The <code>bugherder</code> tag indicates that the comment is from bugherder | |||
* <code>landing</code>, <code>backout</code>, <code>uplift</code> indicate the action taken in bugherder | |||
* The app also posts the link to the commit message, and sets the appropriate release status flags | |||
=== Implementation Notes === | === Implementation Notes === | ||