You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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/[email protected]. Which is not consistent.
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.
The text was updated successfully, but these errors were encountered:
Problem
Our
raycast/extensions
is usingraycast/github-actions/setup-git@master
andraycast/github-actions/git-commit@master
. But inraycast/github-actions
, theraycast/github-actions/git-commit
is using theraycast/github-actions/[email protected]
. 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
andraycast/github-actions
on every update. And it's easier to keep your usages both inraycast/extensions
andraycast/github-actions
consistent.The text was updated successfully, but these errors were encountered: