FR: Closes #m and #n should close m and n

For example here:

https://github.com/Rdatatable/data.table/pull/3837

On GitLab, the parser detects and auto-flags both issues for closing. Only realizing just now that GitHub does not recognize this pattern, which is much more natural language than closes #m closes #n, etc.

Hi @michaelchirico,

Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

1 Like