docs: describe the actual publishing workflow - #12
Merged
Conversation
README documented a tag-triggered workflow and a release.sh that never existed. Publishing is the workflow added in #9.
✅ Deploy Preview for authorizer-helm-chart ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 README described a tag-triggered release workflow and a
release.shthat syncappVersion— neither has ever existed in this repo (no tags, no releases, no such script). Replaced with what actually happens now, plus a warning about CI-skip markers, which caused #11.Merging this also deploys the already-committed
charts/authorizer-2.2.1.tgz, which two skipped Netlify builds left unserved.