-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update the PR description for auto webassets udpates #10212
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hatched
reviewed
Feb 8, 2022
LGTM, except for the fact that the script could use a comment on what are we doing with sed, as pointed out by @hatched . |
Tener
approved these changes
Feb 8, 2022
9ad6b85
to
0f7d2a9
Compare
ibeckermayer
approved these changes
Feb 8, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kimlisa
approved these changes
Feb 8, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for fixing this! 🚀
0f7d2a9
to
fb05cda
Compare
nklaassen
approved these changes
Feb 8, 2022
The script for updating webassets uses the commit message from webapps as the commit message for the PR to teleport. This commit message is almost always a merged PR, which has the format: do some awesome thing (#123) Where '#123' is the number of the **webapps** PR that was merged. The problem with this is, when the teleport PR is created, it interprets the #123 as the number of a **teleport** PR. And since the Teleport repo has a lot more issues/PRs than webapps, Github ends up linking to an old and completely unrelated PR. Fix this by replacing (#123) with (gravitational/webapps#123), which Github correctly renders as a link to the webapps PR in question.
fb05cda
to
5ac7f03
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The script for updating webassets uses the commit message from
webapps as the commit message for the PR to teleport.
This commit message is almost always a merged PR, which has the format:
Where
#123
is the number of the webapps PR that was merged.The problem with this is, when the teleport PR is created, it interprets
the
#123
as the number of a teleport PR. And since the Teleport repohas a lot more issues/PRs than webapps, Github ends up linking to an old
and completely unrelated PR.
Fix this by replacing
(#123)
with(gravitational/webapps#123)
, whichGithub correctly renders as a link to the webapps PR in question.