Skip to content

Create a branch to support major wildcard version #4

Description

@LitoMore

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Severity

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions