Update branch descriptions for e2e test workflows #4732
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.
Changes proposed in this Pull Request:
This PR is a follow-up to #4727, which added a new workflow to manually trigger e2e tests across branches. However, @diegocurbelo flagged some concerns with the descriptive text and the fact that we have two branch variables.
This PR addresses one aspect of the comment now that we have some runs in place. At present, I am still keeping the custom branch input, as I think we may have situations where we want to run workflow code from one branch (such as for a PR), but target code from another branch (generally the e2e tests). Regardless, the changes in this PR only update the description for the
branch
input to reflect that the code will default to the same branch as the workflow branch if no other value is specified.Testing instructions
Inspection should be sufficient.
Changelog entry
Changelog Entry Comment
Comment
No need for a changelog entry as this only impacts the field descriptions for manually running workflows in the GitHub UI.
Post merge