| Summary: | Rewrite https://bugs.gentoo.org/show_bug.cgi?id=XYZ URLs as https://bugs.gentoo.org/XYZ, not vice versa | ||
|---|---|---|---|
| Product: | Gentoo Infrastructure | Reporter: | Coacher <itumaykin+gentoo> |
| Component: | Bugzilla | Assignee: | Bugzilla Admins <bugzilla> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | leio, mgorny |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=630592 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Coacher
2017-02-05 08:48:20 UTC
Commit messages should imho be with a tag like Gentoo-bug: 123456 Though if it's nice and short, I might consider using the full URL too, I suppose. A straight swap currently wouldn't work for aliases, e.g https://bugs.gentoo.org/show_bug.cgi?id=gnome-3.22 /me goes makes a "show_bug.cgi" alias? Anyhow, not infra, just thought to share my thoughts and observation about aliases together with CCing. I agree w/ leio that it's not going to work for aliases. It will also lose links to exact comments during the redirect. Coacher: Why is the long form a problem for you? I've actually been thinking that we should move to what seems be a more standardized form in other projects (popularized by GitHub): "Fixes: $FULL_URL" "See-Also: $FULL_URL" (In reply to Robin Johnson from comment #2) > Coacher: > Why is the long form a problem for you? > > I've actually been thinking that we should move to what seems be a more > standardized form in other projects (popularized by GitHub): > "Fixes: $FULL_URL" > "See-Also: $FULL_URL" Commit messages are my "problem". I am a proxied maintainer and I was asked before to write bug URLs as 'https://bugs.gentoo.org/XYZ' when referencing them from commit messages. I can see that some other devs outside of proxy-maint community use this kind of links for bug URLs in commit messages. It's not a problem per se, but it becomes annoying to manually shorten bug URLs after a while. It would be nice to be able to avoid this manual work and just select URL and do middle-click. (In reply to Coacher from comment #3) > (In reply to Robin Johnson from comment #2) > > Coacher: > > Why is the long form a problem for you? > > > > I've actually been thinking that we should move to what seems be a more > > standardized form in other projects (popularized by GitHub): > > "Fixes: $FULL_URL" > > "See-Also: $FULL_URL" > Commit messages are my "problem". > I am a proxied maintainer and I was asked before to write bug URLs as > 'https://bugs.gentoo.org/XYZ' when referencing them from commit messages. Hmm, I think having that a policy doesn't provide much actual value. > I can see that some other devs outside of proxy-maint community use this > kind of links for bug URLs in commit messages. It's not a problem per se, > but it becomes annoying to manually shorten bug URLs after a while. It would > be nice to be able to avoid this manual work and just select URL and do > middle-click. As an intermediate step, you could use a commit-msg hook to shorten the URL (be sure to not shorten it if there is a reference to a specific comment). I don't see a problem enabling the requested redirect + rewrite, for numerical bug ids that is. Aliases should probably stay at long form, though I don't really see why we would reference aliased bugs in commit messages -- they're mostly trackers, right? This happens when you try to enter a short bug URL to See Also field: https://bugs.gentoo.org/123456 is not a valid URL to a bug. See Also URLs should point to one of: show_bug.cgi in a Bugzilla installation. A bug on launchpad.net. An issue on code.google.com. A bug on bugs.debian.org or debugs.gnu.org. An issue in a JIRA installation. A ticket in a Trac installation. A bug in a MantisBT installation. A bug on sourceforge.net. An issue/pull request on github.com. A task on a Flyspray tracking system. An issue on bitbucket.org. A Review Board review request. An issue in a Rietveld installation. A ticket in an RT installation. A topic on getsatisfaction.com. A bug on bugs.php.net. An issue in a Redmine installation. A bug in a Savane installation. A task in a Phabricator installation. Let's close this in favor of bug #630592 (implemented). |
