Skip to content

project argument works differently with the --web flag #1309

@AliabbasMerchant

Description

@AliabbasMerchant

Describe the bug

Without the --web mode, passing the project name in the project flag, works properly.
However, using the --web mode, we need to pass the project path, because GitHub takes the project path as the query parameter
Version of gh: master

Example

Suppose I have a project named "My Project" in my repo, "testingCLI"
For the non-web version, this works:
gh issue create -t Title -b Body -p "My Project"
For the web version, I need to change it to:
gh issue create -t Title -b Body -p "AliabbasMerchant/testingCLI/1" --web

Possible Solution

Either:

  1. We accept the project name everywhere, and convert the name to the path in the web mode (This may cause conflicts when the org and the repo has projects with the same name; But is not a breaking change)
  2. We accept the project path everywhere, and convert the path to the name in the normal mode (This may be a breaking change for our users, but will help determine the project much more specifically)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority-3Affects 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