raycast / raycast/github-actions
Create a branch to support major wildcard version
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 40
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Problem
Our raycast/extensions is using raycast/github-actions/setup-git@master and raycast/github-actions/git-commit@master. But in raycast/github-actions, the raycast/github-actions/git-commit is using the raycast/github-actions/setup-git@v1.16.0. Which is not consistent.
Solution
See https://github.com/actions/toolkit/blob/main/docs/action-versioning.md.
The solution in the official documentation is to use a v1 tag to manage the major version. But it requires you update the tag with --force on every update.
A better solution is to use a branch called v1 and keep our code in this branch.
Benefits
We don't need to update all versions for raycast/extensions and raycast/github-actions on every update. And it's easier to keep your usages both in raycast/extensions and raycast/github-actions consistent.
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
Read the linked GitHub Actions versioning documentation, then inspect how raycast/extensions and raycast/github-actions reference setup-git and git-commit. Create the v1 branch strategy described in the issue and verify that both repositories can use consistent major-version references without per-update version changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, shell
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100