Skip to content

github_token input does not work on Forgejo Actions #72

@Maks1mS

Description

@Maks1mS

In #34, the github_token field was introduced. However, in the latest version v4 (4.7.0), it no longer works:

git-cliff-x86_64-unknown-linux-gnu.tar.gz
Getting git-cliff v2.11.0 from https://api.github.com/repos/orhun/git-cliff/releases/tags/v2.11.0
curl: (22) The requested URL returned error: 401
⚙️ [runner]: exitcode '22': failure

It looks like it broke after #61 (82629b3).

Using ${{ env.GITHUB_TOKEN || inputs.github_token }} is a bad idea because Gitea/Forgejo Actions set GITHUB_TOKEN. Also, it seems this is already handled by default: "${{ github.token }}", which is equal to env.GITHUB_TOKEN by default.

Maybe we need something like this:

  github_token:
    description: "GitHub API token"
    required: false
    default: "${{ env.GITHUB_TOKEN || github.token }}"

But that looks overcomplicated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions