You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document that bpo issues can be automatically closed using commit message #502
One thing I wanted to point out from https://help.github.com/en/articles/closing-issues-using-keywords
is that it would be nice to incorporate resolve, resolves, resolved into this regex. I would be more than happy to integrate this change into psf/bpo-roundup, let me know your thoughts and if there are any additional processes involved in proposing this change apart from raising an issue and a PR.
@rahul-kumi I think it's a great suggestion. I'm not actually involved in bpo development, so perhaps the bpo maintainers can give you better guidance on how to contribute there.
From my perspective though, considering that we'll be migrating away to GitHub Issues, I think at this point it's not worth making such change to b.p.o. I do think it would still be great to document the existing behavior.
Activity
webknjaz commentedon Jun 29, 2019
Better follow what GitHub has: https://help.github.com/en/articles/closing-issues-using-keywords
This way people won't have to relearn which words work on which platform
PEP 581 Updates (#1114)
Mariatta commentedon Jul 11, 2019
Reading bpo's source code, the magic words are matching this regex
kumiDa commentedon May 17, 2021
@Mariatta, as per the below regex I understand that the matched words are -
close,closes,closedclosing,fix,fixes,fixedOne thing I wanted to point out from https://help.github.com/en/articles/closing-issues-using-keywords
is that it would be nice to incorporate
resolve,resolves,resolvedinto this regex. I would be more than happy to integrate this change into psf/bpo-roundup, let me know your thoughts and if there are any additional processes involved in proposing this change apart from raising an issue and a PR.Mariatta commentedon May 17, 2021
@rahul-kumi I think it's a great suggestion. I'm not actually involved in bpo development, so perhaps the bpo maintainers can give you better guidance on how to contribute there.
From my perspective though, considering that we'll be migrating away to GitHub Issues, I think at this point it's not worth making such change to b.p.o. I do think it would still be great to document the existing behavior.
fixes python#502: include infromation about auto-closure of bpo isssues
kumiDa commentedon May 18, 2021
Thanks for the clarification @Mariatta.
I have raised PR #701 documenting the feature.
Let me know if any improvement is to be made to the PR.
ezio-melotti commentedon May 5, 2022
Since we migrated to GitHub, this can be closed.