Open
Conversation
Contributor
Author
|
Please let me know if you have questions or if this requires any changes. Thanks! |
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
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.
This pull request introduces a set of improvements to the build and release workflow for the project, primarily focusing on automating version management during manual releases.
Build and Release Workflow Automation:
version_bumpandis_beta) to.github/workflows/build-action-artifacts.yml, allowing users to specify the type of version bump (patch, minor, major) and whether the release is a beta.app/build.gradle.ktsbased on workflow inputs, including incrementing the version code and tagging the release in Git.Developer and release workflow recommendation
I also recommend if you need to update your feature branch with new changes from other PRs that have merged to main, to do so via
git pull --rebase origin mainon your feature branch. This will create and keep a clean and linear git history which makes troubleshooting, git bisect, reverts, etc. much more straight forward.The reason I recommend branching off main for a feature and merging it into main via PR: run tests on PR to validate. Only merge when feature is ready. It helps keep main releasable at all/or most of the time. This is important given if this is not the case, you have to manually keep track of what commit/when main is stable enough to release. This also is the same process for external contributors.