(Based on PSA in https://groups.google.com/a/chromium.org/d/msg/chromium-dev/rXYPzakFy0E/WafliQVuaWoJ) Below is the specification of officially supported formats, based on the previous patterns and observed usage (regression tested against thousands of actual commit messages). The pattern-matching rules are still fairly loose, so some not-quite-right formats, like "BUG====n", may work, but are not guaranteed. Please let me know if you encounter any formats that you expect to work but which don't. Supported Syntax: ---------------------------- BUG=n BUG n BUG:n Matches issue 'n' in the default issue tracker for the repository (e.g. skia tracker for skia repos, chromium tracker for chromium and blink, etc.). BUG=project:n BUG project:n BUG:project:n Matches issue 'n' in the issue tracker for 'project'. BUG=<Issue Tracker URL> A direct link to an issue tracker page matches that issue. Syntax Notes: - The keywords 'BUG' and 'ISSUE' are interchangeable in all formats. - 'n' can be a comma-delimited list of bug #'s. - If 'n' is a list, all items belong to the most recent project specifier preceding the list, e.g.: BUG=projectA:1,2,3,projectB:8,9 is equivalent to: BUG=projectA:1,projectA:2,projectA:3,projectB:8,projectB:9 - Multiple bug lines may appear in the commit message. - Project/URL specification only works for configured projects [2]. ---------------------------- [1] [2] Where "universal" is defined as the set of known projects [3] configured for each repo. For instance, a bug in the blink repo can specify "BUG=chromium:n", but not "BUG=skia:n", because that just seems unlikely. If you encounter a case where one project should be able to create bugs for another, but can't, let me know. [3] "Known projects" are the issue trackers which have been configured to allow read/write access for the bugdroid account, currently chromium, nativeclient, webrtc, v8, and skia. |
For Developers > Contributing Code >