pantheon-systems / pantheon-systems/terminus-github-actions
v2: Stop updating major-version branch
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 18
- Forks
- 13
- Avg merge
- 22h 4m
- Merged PRs (30d)
- 2
Description
Summary
Stop creating/updating the floating v1 major-version branch on release. Consumers should pin by SHA with an exact version tag comment instead.
This is a breaking change for consumers currently pinned to @v1 (the branch), which is why it belongs in a major version bump. Consumers pinned by SHA are unaffected.
Work
- Remove or disable the major-version branch update from the release workflow
- Update documentation to recommend SHA pinning:
uses: pantheon-systems/terminus-github-actions@<sha> # v2.0.0 - Leave existing
v1branch in place — it just stops being updated
Context
- Jira: SITE-5948
- Epic: SITE-5932
- Background: scratchpad PR #331, release-pipeline-actions-plan.md item 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the release workflow that creates or updates the floating major-version branch, then find the documentation showing how consumers pin this action. Verify that the workflow no longer updates the branch, the existing v1 branch remains untouched, and the documentation recommends SHA pinning with an exact version tag comment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100