starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #317] Action not being discovered for list #223

New issue

Closed

opened 2026-03-01 21:41:29 +03:00 by kerem · 10 comments

kerem commented

2026-03-01 21:41:29 +03:00

Owner

Originally created by @timheuer on GitHub (Jul 24, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/317

Ex repo: https://github.com/timheuer/issue-notifier

When running act -l my action is not being discovered despite it being located in the correct location of .github\workflows and a valid action.

Originally created by @timheuer on GitHub (Jul 24, 2020). Original GitHub issue: https://github.com/nektos/act/issues/317 Ex repo: https://github.com/timheuer/issue-notifier When running `act -l` my action is not being discovered despite it being located in the correct location of `.github\workflows` and a valid action.

kerem

2026-03-01 21:41:29 +03:00

closed this issue
added the
area/cli

meta/resolved

area/docs
labels

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Sep 23, 2020): Issue is stale and will be closed in 7 days unless there is new activity

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@jarretmoses commented on GitHub (Sep 24, 2020):

I am also having this issue

@jarretmoses commented on GitHub (Sep 24, 2020): I am also having this issue

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@joelworsham commented on GitHub (Oct 2, 2020):

Same

@joelworsham commented on GitHub (Oct 2, 2020): Same

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@raethlein commented on GitHub (Oct 21, 2020):

@timheuer By default, act only considers workflows that use the default push event. Since your action only "listens" to the "issues" event, you have to execute the act command as following: act issues -l which then lists your action correctly (I just tested it on my Mac). I created a pull request #399 to make this more clear in the documentation. Do you think the suggested documentation update would have had helped?

@raethlein commented on GitHub (Oct 21, 2020): @timheuer By default, `act` only considers workflows that use the default `push` event. Since your action only "listens" to the "issues" event, you have to execute the `act` command as following: `act issues -l` which then lists your action correctly (I just tested it on my Mac). I created a pull request #399 to make this more clear in the documentation. Do you think the suggested documentation update would have had helped?

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@mtfurlan commented on GitHub (Dec 18, 2020):

So I never actually read those parts of the readme, I just ran act --help and all it says there is

Usage:
  act [event name to run] [flags]
...
 -l, --list                   list workflows

As [whatever] means whatever is optional, I think it's pretty reasonable to assume that act --list will list all workflows.
Also in the case of --list the event isn't being run.

So maybe something similar to

Usage:
 act [event name to operate on or run] [flags]
 If no event name passed, will default to "push"
...
-l, --list                   list workflows triggered by event being operated on

It would honestly be more useful if act --list just did list all workflows unless you pass a specific event, but in the meantime it would be helpful if the docs were correct.

@mtfurlan commented on GitHub (Dec 18, 2020): So I never actually read those parts of the readme, I just ran `act --help` and all it says there is ``` Usage: act [event name to run] [flags] ... -l, --list list workflows ``` As `[whatever]` means whatever is optional, I think it's pretty reasonable to assume that `act --list` will list *all* workflows. Also in the case of `--list` the event isn't being run. So maybe something similar to ``` Usage: act [event name to operate on or run] [flags] If no event name passed, will default to "push" ... -l, --list list workflows triggered by event being operated on ``` It would honestly be more useful if `act --list` just *did* list all workflows *unless* you pass a specific event, but in the meantime it would be helpful if the docs were correct.

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 18, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Jan 18, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@mtfurlan commented on GitHub (Jan 18, 2021):

I think at the very least the help text should be updated to be less misleading.

@mtfurlan commented on GitHub (Jan 18, 2021): I think at the very least the help text should be updated to be less misleading.

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@catthehacker commented on GitHub (Jan 21, 2021):

@mtfurlan I've updated README and in-act help as part of https://github.com/nektos/act/pull/486

@catthehacker commented on GitHub (Jan 21, 2021): @mtfurlan I've updated README and in-`act` help as part of https://github.com/nektos/act/pull/486

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@mtfurlan commented on GitHub (Jan 21, 2021):

Cool, thank you!

@mtfurlan commented on GitHub (Jan 21, 2021): Cool, thank you!

kerem commented

2026-03-01 21:41:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 21, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Feb 21, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem referenced this issue

2026-03-01 21:50:57 +03:00

[PR #223] [MERGED] Implement UnmarshalYAML for ActionRunsUsing #1387

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#223

No description provided.

Rows
Columns