mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #227] Support targeting specific workflows #156
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#156
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rbellamy on GitHub (May 8, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/227
With multiple workflows it is possible to have workflows and jobs with non-unique IDs.
one.yml
two.yml
Right now the ability to target a job when working with multiple workflows requires that the job have a unique ID.
I think the best option would be to allow the
-Wflag to accept an array of workflow files (new feature) or a directory (current functionality).I'm a novice at Go or I would create a PR. If it's relatively simple, and someone could give me some pointers, I'd be glad to give it a shot. I've looked at the code, and am unsure where to start.
@arbourd commented on GitHub (May 23, 2020):
Agreed. I use Actions in a monorepo and each microservice gets 1-2 workflows. I just delete the other ones I'm not testing locally right now, which isn't really inconvenient.
Repurposing the -W flag would be really easy but I'm not sure if the maintainers would like a dual-purpose flag.
@cplee commented on GitHub (May 26, 2020):
I like the option of
-Wsupport a list of files or directory. Open to PRs on this if someone wants to do it!@arbourd commented on GitHub (May 27, 2020):
Thanks for the quick turn around @cplee.