updatecli: link to the original Pull Request #2217
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
In addition to the GitHub commit to help with tracking the consumers
reakaleek
previously approved these changes
Nov 7, 2023
v1v
commented
Nov 7, 2023
|
In other words, this change will modify PRs like #2197, that won't contain the link to the commit but also the PR. 
|
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.
What
Add the original Pull Request that contains the changes in the specs to be in the description of the Pull Request created with the
updatecliautomation. This will help with track what APM Agents use it.Test
Given the updatecli and gh cli
When running
$ GIT_USER=foo \ GIT_EMAIL=1 \ GITHUB_TOKEN=*** \ updatecli apply --config .ci/updatecli.d/update-gherkin-specs.yml --push=false --debugThen