Skip to content

Undocumented behaviour of the -w flag for gh run list  #9038

@joshuajtward

Description

@joshuajtward

Describe the bug

The -w flag for gh run list behaves differently depending on whether a workflow name or a workflow filename is passed to it. Specifically, if a workflow has been manually disabled then the gh run list -w will only return values with the filename as input, and nothing is returned for the workflow name (assuming no duplicate workflow names...).

Versions checked: 2.44.1, 2.48.0

Steps to reproduce the behavior

  1. In a repository with a workflow which has been manually disabled
  2. Run gh run list -w my-workflow-name and observe that no runs are found
  3. Run gh run list -w my-workflow-name.yml and observe that previous runs are listed (potentially as expected?)

Expected vs actual behavior

Given the nature of workflow naming I can see reasonable grounds for this being a desirable feature of the CLI, so the scope of this issue is just to get the behaviour included in the documentation. If it turns out to be undesirable behaviour then I am happy to raise that as another issue!

Logs

screenshot showing gh run list output

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggh-runrelating to the gh run commandhelp wantedContributions welcomep3Affects a small number of users or is largely cosmetic

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions