fix: correct branch trigger from main to master (upstream default branch)#16
Merged
Merged
Conversation
- workflow triggers were set to main but upstream repo uses master - README install URLs and script headers point to master - install.sh ARM arch tag: Arm64 -> ARM64 to match GHA runner.arch
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
2 participants
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 build workflow wasn't triggering because I had branch name 'main' on my fork, and here we have 'master' branch. Classical example of "it works on my machine".
How to create new tag/release:
website - go to
https://github.com/Doorman11991/smallcode/releases/newterminal - something like
(CI should create the release + tarballs)
Also, automating changelog text for releases made with new version tag.
Added a workflow step that auto-extracts the matching section from CHANGELOG.md based on the tag version and passes it as the release body. Now
git push v0.X.Xproduces a complete release with tarballs + changelog — zero manual steps.How it works
releasejob extracts the## [X.X.X]section from CHANGELOG.md using awksoftprops/action-gh-releasecreates the release with the extracted notes + tarballsEdge cases handled:
v0.2.5-test→ no match, no error