Some feature requests

[data-man]

I'm using your awesome app every day, thank you!
And GitHub CLI too. :)
So, my proposed commands:

• add gcli repos search command, like gh search repos
• add gcli repos list command, like gh repo list
• add gcli repo view command, like gh repo view

But honestly, I haven't looked into whether all supported gcli source providers have a necessary API.
What do you think?

[herrhotzenplotz]

Hej @data-man!

I'm using your awesome app every day, thank you!

Thanks! I hope you're spreading the word about it too! :-)

So, my proposed commands:

• add gcli repos search command, like gh search repos
• add gcli repos list command, like gh repo list
• add gcli repo view command, like gh repo view

This sounds great. A few thoughts:

gcli repos list

This already exits via gcli repos.

gcli repos search

This should be (famous last words) sort of easy to implement for all the forges we try to support.
Though, to make it consistent with both gcli pulls and gcli issues which already support searching I would reduce the syntax to:

gcli repos [search-terms...]

The idea is that when not specifying search terms you get everything without filtering by search terms.

gcli repo view

I'll have to do some research as to what this should display.
Or maybe you could suggest what this should do.
@gjnoonan already brain dumped on IRC so I'll just quote:

we could reuse gcli_repo_print for the view command, and just add grabbing Readme.

Maybe this is already enough?

As for the proposed commands you mentioned above: We could add
aliases for UX, but I'm just worried that this would conlict with
the search feature; we've had issues with ambiguity of the command
line options previously related to exactly this.

[data-man]

Thanks! I hope you're spreading the word about it too! :-)

Yes, I regularly post news about gcli on https://www.linux.org.ru/tag/gcli. I'm one of the moderators of this forum. :)

This already exits via gcli repos.

OMG, sorry! I forgot about -t type option!
Well, I'd like to see a programming language in each repository.

gcli repo view

I'll have to do some research as to what this should display.
Or maybe you could suggest what this should do.

gh displays the README.md file, if it exists.

The full description:

$ gh repo view -h
Display the description and the README of a GitHub repository.

With no argument, the repository for the current directory is displayed.

With `--web`, open the repository in a web browser instead.

With `--branch`, view a specific branch of the repository.

For more information about output formatting flags, see `gh help formatting`.

USAGE
  gh repo view [<repository>] [flags]

FLAGS
  -b, --branch string     View a specific branch of the repository
  -q, --jq expression     Filter JSON output using a jq expression
      --json fields       Output JSON with the specified fields
  -t, --template string   Format JSON output using a Go template; see "gh help formatting"
  -w, --web               Open a repository in the browser

INHERITED FLAGS
  --help   Show help for command

JSON FIELDS
  archivedAt, assignableUsers, codeOfConduct, contactLinks, createdAt,
  defaultBranchRef, deleteBranchOnMerge, description, diskUsage, forkCount,
  fundingLinks, hasDiscussionsEnabled, hasIssuesEnabled, hasProjectsEnabled,
  hasWikiEnabled, homepageUrl, id, isArchived, isBlankIssuesEnabled, isEmpty,
  isFork, isInOrganization, isMirror, isPrivate, isSecurityPolicyEnabled,
  isTemplate, isUserConfigurationRepository, issueTemplates, issues, labels,
  languages, latestRelease, licenseInfo, mentionableUsers, mergeCommitAllowed,
  milestones, mirrorUrl, name, nameWithOwner, openGraphImageUrl, owner, parent,
  primaryLanguage, projects, projectsV2, pullRequestTemplates, pullRequests,
  pushedAt, rebaseMergeAllowed, repositoryTopics, securityPolicyUrl,
  squashMergeAllowed, sshUrl, stargazerCount, templateRepository, updatedAt, url,
  usesCustomOpenGraphImage, viewerCanAdminister, viewerDefaultCommitEmail,
  viewerDefaultMergeMethod, viewerHasStarred, viewerPermission,
  viewerPossibleCommitEmails, viewerSubscription, visibility, watchers

LEARN MORE
  Use `gh <command> <subcommand> --help` for more information about a command.
  Read the manual at https://cli.github.com/manual
  Learn about exit codes using `gh help exit-codes`
  Learn about accessibility experiences using `gh help accessibility`

[data-man]

I saw your libtbl project. Let's use it in gcli! :)

[herrhotzenplotz]

Yes, I regularly post news about gcli on https://www.linux.org.ru/tag/gcli. I'm one of the moderators of this forum. :)

Good stuff! Thank you very much!

Well, I'd like to see a programming language in each repository.
...
gh displays the README.md file, if it exists.

Ok yeah that makes sense.

If you or @gjnoonan wish to work on this please let me know so we don't duplicate work - maybe even talk on IRC about this.
Also, I guess this will go in after the next release which I am anticipating within the next 14 days or so.

I saw your libtbl project. Let's use it in gcli! :)

Haha in fact, libtbl is extracted from gcli. It was originally developed in-tree in gcli and then pulled out because I thought it would be useful for others. The version in gcli has some extensions that are specific to gcli which why it's not a "real external dependency" and still fully in-tree.

[herrhotzenplotz]

@data-man I've pushed an initial implementation of repository search to the nsonack/repo-search branch.

At your leisure, take a look, test, break it etc :-)

A view action on repositories will be a separate set of patches.