Check out the HEAD of the release branch for tag events #898
+102
−0
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
Tags aren't necessarily made to the HEAD of the version branch. The documentation to be published is always on the HEAD of the release branch. Because the workflow now uses regular expressions in Bash, inputs must now use Extended Regular Expression syntax. Signed-off-by: Jack Baldry <[email protected]>
Signed-off-by: Jack Baldry <[email protected]>
robbymilo
approved these changes
Nov 26, 2024
jdbaldry
commented
Nov 26, 2024
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.
I'll use the documentation and new code to release a v2.0.0-rc.1 of the
publish-technical-documentation-*actions.I can then test that release candidate out in
grafana/grafanaand ensure that it works properly before release v2.0.0 proper.Tags aren't necessarily made to the HEAD of the version branch. The documentation to be published is always on the HEAD of the release branch.
Because the workflow now uses regular expressions in Bash, inputs must now use Extended Regular Expression syntax.
Similar code was already used in grafana/grafana but wasn't ported to this composite action.