-
Notifications
You must be signed in to change notification settings - Fork 114
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
get-metadata: should we accept "Fixes" and "Refs" without ":"? #127
Comments
I am a bit afraid this would give many false positives and we have to end up with struggling with natural language processing (I don't have problem with that but it's a really big undertake if you want to get it right). So the easiest solution is: if people don't follow the format, just ignore it. |
@joyeecheung I am a bit concerned that people may use GitHub syntax that does not require |
Well, they might indeed, but the syntax only works when the branch is merged according to the doc you linked, I don't know if it works with our process. Anyway, I'm +1 with @joyeecheung , the formatting exists for a reason IMHO, I don't think we should make allowance or we risk having more problems than now. |
is it detected by a regexp now? |
@targos Yea it's deteced by regular expressions in |
What about something like this? /(Close[ds]?|Fix(e[ds])?|Resolve[sd]?)\s*:?\s*https?:\/\/(\S+)/i; I think we require full URLs already so this should be fine and without false positives. That said, I'm not sure we should encourage this syntax. Maybe it could be normalized by |
Agreed, having |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
i'd say we should close this - I see no real reason to deviate from syntax we've been adhering to for years. Feel free to open again if yall have other thoughts! |
Refs: in the nodejs/node#17295, the
Fixes https://github.com/nodejs/node/issues/17294
commit message line was not included in the metadata.The text was updated successfully, but these errors were encountered: