-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Gitlab closing comma separated actions #37
Comments
The reason is that I mostly based the code on the GitHub behavior. Can you confirm that in GitLab when closing a PR with |
Hi @pvdlg , for context, i made some projects at GitLab:
Default Examplehttps://gitlab.com/angelkenneth/issue-closing-sample/merge_requests/1
This Merge Request closes the issues № 20, № 21, № 18, and № 19, but not № 23 for some reason. Aside: I think № 23 not being closed is a bug, because i was able to do something similar at the 3rd example. I need to do more research if this issue has been raised or not at a future time. 2nd Examplehttps://gitlab.com/angelkenneth/issue-closing-sample/merge_requests/2
This closes issues № 11 and № 15. 3rd Examplehttps://gitlab.com/angelkenneth/issue-closing-sample/merge_requests/4
This closes external issues № 16 and № 12. |
Thanks for those info! Doing that would be a big rewrite of all the regexp in this project so it might takes time... |
hi @pvdlg Any updates on this? i wasn't aware that by github doesn't work that way normally. I'm working on a custom action to handle, e.g.: "blocked by: #2001, #2004". |
Parser configuration
Text to parse
From: Managing Issues > Default closing pattern
Current Behavior
Expected behavior
Issue 19 and 23 should be interpreted as close.
If it helps, their parser code is at: closing_issue_extractor.rb
The text was updated successfully, but these errors were encountered: