3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
It's correct that, if you want to have different workflows per branch, one workflow will be inactive in each branch. Would you prefer to be able to hide inactive workflows in the future?
1
The BranchName workflow source variable will reference the current branch, though I can't think of a way to trigger workflows based on that. Let us know if this helps!
Thanks this is a good step. I Will try it out.
1
yeah. It will be so much cleaner on the dashboard.
Also is there a way to reference the current branch in the yml config file? In GH-Actions you could do something like github.ref. This way we could have conditional triggers based on current branch
con risposta 5 mesi fa
Contenuto pertinente
AWS UFFICIALEAggiornata 3 anni fa- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Hide inactive would be good. Also maybe a global setting to only use workflows for a named list of branches. My environment can have a lot of branches which makes the workflows dashboards horrible.