Skip to content

workflow that uses GITHUB_O+TOKEN can no longer trigger other workflow! #131

@eranturgeman

Description

@eranturgeman

Hello!
Im developing a git bot that can be integrated with Github.
Up until now we used the auto-generated GITHUB_TOKEN for this product so it can create new PRs in a git repository.
The bot can be triggered manually or periodically as an Github Action.
So far it worked fine but suddenly whenever a new PR is opened by the bot's action it will not trigger other workflows that should be triggered in the repository.
I read your docs that using GITHUB_TOKEN doesn't allow a workflow to trigger another workflow.
I wanted to ask when this change was introduced? We didn't experience this issue so far.
Is using GitHub app token or private token the only replacements I can use to achieve what I want?
Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions