[core-workflow] Choosing a prefix/label for issue numbers
Berker Peksağ
berker.peksag at gmail.com
Wed Feb 8 21:54:49 EST 2017
On Wed, Feb 8, 2017 at 9:03 PM, Senthil Kumaran <senthil at uthcode.com> wrote:
> _If we decide to rewrite_, I see the following areas of improvement.
>
> 1) Rename #NNNN, Issue #NNNN, issue #NNNN, IssueNNNN, issueNNNN to bpo-NNNN
> 2) Looking for numbers 1000 and above which don't start with SF, is
> okay with me as it can reduce the false positives.
Count me as -1 for history rewrite. There are many different commit
message styles and we probably will miss some edge cases :)
> Also, other feedback from Martin was to not have hg branch annotation.
> E.g: https://github.com/orsenthil/cpython-migration-test/commit/851c48a
>
> That can be removed. I am unable to decide on the merits/de-merits.
> hg-git tool seems to be doing that commit extra messages by default.
> The annotation gives information that commit was originally done in
> that particular hg branch.
+1 for removing the branch annotation. +0 if there is no easy way to do it.
Thank you for working on this, Senthil!
--Berker
More information about the core-workflow
mailing list