[Python-Dev] GH-NNNN vs #NNNN in merge commit (original) (raw)
Eric V. Smith eric at trueblade.com
Thu Jan 25 20:32:41 EST 2018
- Previous message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Next message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 1/25/2018 8:13 PM, Terry Reedy wrote:
On 1/25/2018 7:47 PM, Mariatta Wijaya wrote:
I think we're starting to deviate from the original topic here which is: please replace # with GH- when you click Squash & Merge button. I will try to remember to do this, although it seems pointless if most people do not.
I sometimes forget, too.
Since changing this in the github workflow seems hard, how about sending an email to the committer after the commit if this mistake is detected? I know that in my case, if I were reminded a few times, I would be better at doing it correctly in the future.
Eric.
- Previous message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Next message (by thread): [Python-Dev] GH-NNNN vs #NNNN in merge commit
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]