Gitflow-esque release flow for applications #11
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
webgrip/workflows#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ryangr0 on GitHub.
Originally assigned to: @Ryangr0, @Copilot on GitHub.
Description
I want that when PRs into development are merged, a release PR from development to main is made, with https://keepachangelog.com/en/1.1.0/ standard.
Additional Context
https://github.com/webgrip/firefly-iii-application/blob/development/.github/workflows/on_source_change.yml This is what applications currently use. As you can see, a semantic release is done, and then that new version is immediately deployed with helm. I want a push to all branches to kick off static analysis and tests, and only if those succeed, should the semantic release step be done. (and only on main).
Feel free to give feedback or make your own decisions.