gh cli returns different (and incorrect) first entry than what is returned from the ui

Describe the bug

A clear and concise description of what the bug is. Include version by typing gh --version.

 -→ gh version
gh version 2.49.1 (2024-05-08)
https://github.com/cli/cli/releases/tag/v2.49.1

 -→ cat /etc/os-release 
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="23.11.6418.e402c3eb6d88"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 23.11 (Tapir)"
SUPPORT_END="2024-06-30"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="23.11 (Tapir)"
VERSION_CODENAME=tapir
VERSION_ID="23.11"

I am trying to find the last issue number in the repo. i use that to create an issue automatically. its alrways returning the wrong results

Steps to reproduce the behavior

Type this gh issue list -L 10 --repo unnug/pf-track --search "sort:created-desc" --json number --jq '.[].number'
View the output

See error

Expected vs actual behavior

the ui is correctly reporting the right results as per the attached screencshots

Logs

The first entry in descending order should be issue #631 i am not sure why it is returningthe above

Unless I am misreading something, the UI on your screenshot is showing closed issues while the CLI query is for open issues.

Could you use the --state flag with closed? That should show closed issues, only. Other supported values are open and all

Unless I am misreading something, the UI on your screenshot is showing closed issues while the CLI query is for open issues.

Could you use the --state flag with closed? That should show closed issues, only. Other supported values are open and all

--state all is what i needed exactly ! as you said the ui is implicitly using closed while the cli is again implicitly using open without telling the user about what the query is implicitly using.

Do you think it would make sense to add a hint on the ui/cli to infomr the user what implicit settings are being passed ?

Bast Regards and thank you sooo much !!!

@arunsathiya

Thanks @arunsathiya for triaging this.

Do you think it would make sense to add a hint on the ui/cli to infomr the user what implicit settings are being passed ?

It's in issue list --help:

-s, --state string Filter by state: {open|closed|all} (default "open")

And if you run gh issue list the green is used to indicate state as well:

That said, I would be open to adding a little extra info in the issue list Long description. Do you think it would have helped you if issue list --help would have said:

List issues in a GitHub repository. By default this only lists open issues.

I'm not that keen to repeat information but I also don't want to ignore someone getting confused.

@williammartin

@williammartin thank you so much for this detailed answer and your keen suggestion

what i missed is the --state flag that can be passed.

if you can add an example to the gh issue list --help showing how to use state

  $ gh issue list --state all --search "sort:created-desc"

as you mentioned something along the lines of

List issues in a GitHub repository. By default (if no --state flag is passed)  this only lists open issues.

if you can add an example to the gh issue list --help showing how to use state

Great idea.

I've added the help wanted label if you'd be up for contributing those changes.

Cheers!

@yassinm

@yassinm If you'd like to contribute these changes, you can edit the command description/examples here:

cli/pkg/cmd/issue/list/list.go

Lines 61 to 73 in faef2dd

    
           		Long: heredoc.Doc(` 
        
           			List issues in a GitHub repository. 
        
           			The search query syntax is documented here: 
        
           			<https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests> 
        
           		`), 
        
           		Example: heredoc.Doc(` 
        
           			$ gh issue list --label "bug" --label "help wanted" 
        
           			$ gh issue list --author monalisa 
        
           			$ gh issue list --assignee "@me" 
        
           			$ gh issue list --milestone "The big 1.0" 
        
           			$ gh issue list --search "error no:assignee sort:created-asc" 
        
           		`),

@williammartin

@williammartin If we're adding this, why not add a similar example to gh pr list?

If we're adding this, why not add a similar example to gh pr list?

Sounds like a nice idea to me!

Navigation Menu

Repository navigation

gh cli returns different (and incorrect) first entry than what is returned from the ui #9067

Describe the bug

Steps to reproduce the behavior

Expected vs actual behavior

Logs

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	Long: heredoc.Doc(`
	List issues in a GitHub repository.

	The search query syntax is documented here:
	<https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests>
	`),
	Example: heredoc.Doc(`
	$ gh issue list --label "bug" --label "help wanted"
	$ gh issue list --author monalisa
	$ gh issue list --assignee "@me"
	$ gh issue list --milestone "The big 1.0"
	$ gh issue list --search "error no:assignee sort:created-asc"
	`),

gh cli returns different (and incorrect) first entry than what is returned from the ui #9067

Description

Describe the bug

Steps to reproduce the behavior

Expected vs actual behavior

Logs

Activity

arunsathiya commented on May 9, 2024

yassinm commented on May 10, 2024

williammartin commented on May 10, 2024

yassinm commented on May 10, 2024

williammartin commented on May 10, 2024

babakks commented on May 29, 2024

babakks commented on May 29, 2024

williammartin commented on May 30, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions