Ability to disable all Github Actions workflows more easily
See original GitHub issueRight now I’m not aware of a way to easily disable all Github Actions in an easy manner. To disable the dependency upgrade workflow, I had to pass something like this:
// @ts-ignore
depsUpgrade: {
ignoresProjen: false,
binder() {},
bind() {},
},
I’ve been trying to use Projen in a work environment where we use a different CI solution, and Github Actions simply isn’t enabled in our GHE appliance.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Disabling and enabling a workflow - GitHub Docs
Disabling a workflow · On GitHub.com, navigate to the main page of the repository. · Under your repository name, click Actions. Actions tab...
Read more >Ability to disable Actions workflows | GitHub Changelog
Starting today you can temporarily disable a GitHub Actions workflow either in the UI or through the API. With this functionality you can...
Read more >GitHub Actions: Limit workflow runs & Control permissions for ...
GitHub Actions now supports a concurrency key at both the workflow and job level that will ensure that only a single run or...
Read more >Avoid Duplication! GitHub Actions Reusable Workflows
So, Reusable Workflows in GitHub Actions. Thanks to this feature you can now reference an entire Actions workflow in another workflow, ...
Read more >How to disable GitHub Actions Concurrency - Stack Overflow
As documented "Any previously pending in the concurrency group will be canceled". In others words, the queue is limited in one.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@eladb I took a look at the PR. From what I can tell, Projen now conflates “github actions” with “github”. Is this accurate? From what I can tell, if I wanted Projen to manage issue/PR templates but not Github Actions workflows, I can no longer do this.
Bonus points: have the ability to easily disable individual workflows vs a single on/off switch.