egoavara/Propagate Merger
Automatically propagate hotfix changes across branches using configurable merge strategies
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| mode | Execution mode (branch-create: create hotfix branch, auto-merge: propagate hotfix) | yes | — |
| version | Hotfix target version (required, e.g. v0.1.2) | yes | — |
| hotfix-suffix | Hotfix suffix (required, e.g. hotfix.1) | yes | hotfix.1 |
| github-token | GitHub token for authentication | yes | ${{ github.token }} |
| direct-merge-branches | Stage 1: Direct merge branch patterns (executed first, mode: auto-merge, default: main,release/*) | no | main,release/* |
| update-then-merge-branches | Stage 2: Update then merge branches (executed after direct-merge-branches, mode: auto-merge, default: dev) | no | dev |
| auto-cleanup | Auto-delete hotfix branch after propagation (mode: auto-merge, default: true) | no | true |
Outputs
| name | description |
|---|---|
| hotfix-branch | Created or processed hotfix branch name |
| base-version | Base version tag used for branch creation |
| propagation-result | Propagation result (success/partial/failed) |
| successful-branches | Successfully propagated branches (JSON) |
| failed-branches | Failed propagation branches (JSON) |
| created-prs | Created PR numbers (JSON) |