-
Notifications
You must be signed in to change notification settings - Fork 50
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
Lines with long URLs #24
Comments
Well, AFAIC I'd say yes, it does seem logical otherwise the link will be broken, but I think it should first be discussed as meta in core, or wherever the contribution guides are discussed. I don't think that's quite up to us to decide to change the validation rules on our own. |
Core issue: nodejs/node#17116 |
3 tasks
vsemozhetbyt
added a commit
to nodejs/node
that referenced
this issue
Apr 22, 2018
PR-URL: #20207 Fixes: #17116 Refs: nodejs/core-validate-commit#24 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
@Tiriel Exception approved and landed: nodejs/node#20207 |
jasnell
pushed a commit
to nodejs/node
that referenced
this issue
Apr 23, 2018
PR-URL: #20207 Fixes: #17116 Refs: nodejs/core-validate-commit#24 Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
joyeecheung
pushed a commit
that referenced
this issue
Nov 2, 2018
richardlau
pushed a commit
to richardlau/core-validate-commit
that referenced
this issue
Dec 15, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should we alleviate the 72 characters rule for lines with long URLs?
Example: nodejs/node#17107
The text was updated successfully, but these errors were encountered: