GitHub Community
How do I make a GitHub workflow trigger other workflows without PATs? #25612
-
|
Hi, I’d like to know how I can make a workflow trigger another workflow after it gets pushed without using a personal access token (PAT). I have recently found out that I can use PATs, but I am personally not a fan of that due to manual intervention. I prefer things to be extremely easy to setup and take as less time as possible. The Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
TheEvilSkeleton:
The answer is unfortunately simply “you can’t”. The documentation says the limitation is to prevent accidentally creating recursive workflows, and there is no configuration option to remove it. |
Beta Was this translation helpful? Give feedback.
-
|
This is just awful. They should allow people to set a depth limit on the repo GITHUB_TOKEN with a repo configuration. So I could say the token has a depth=1, which would behave like they do right now. Or I could say it has a depth=2, which means a workflow can trigger another workflow only once. On each use they would just do They could establish a maximum depth limit of 15. If anyone sets that limit and then gets a huge bill, it's their fault. But please don't make people create PATs, that's such an awful security and maintainability practice. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm… is there a way that is more convenient than using PATs? |
Beta Was this translation helpful? Give feedback.
The answer is unfortunately simply “you can’t”. The documentation says the limitation is to prevent accidentally creating recursive workflows, and there is no configuration option to remove it.