How to ‘push’ with gh?

[CQUPTLei]

I am new to gh. I can not find such commands as git add 、git commit 、git push。How can i push my changes with gh ? Is there such commands in gh? such as:

gh repo add
gh repo commit
gh repo push

I do not find it at: https://cli.github.com/manual/gh_repo

If not, what are the advantages of using gh? (I use traditionally Git commands seem to be enough?)

Thanks for your explain！

[mislav]

I do not find it at: https://cli.github.com/manual/gh_repo

There are no gh commands to commit nor push.

If not, what are the advantages of using gh?

GitHub CLI is a tool to interface with GitHub-specific features. GitHub is built around the concepts of Git repositories and adds extra features on top:

• Users, organizations, access-controlled repositories,
• Issues, Discussions,
• Pull Requests, code review,
• GitHub Actions, Codespaces,
• Gists,
• and more.

Git CLI can already create local git repositories, commit, add remotes, push, etc. There doesn't need to be an additional CLI to do the same. However, Git CLI cannot create a GitHub repository, or list its issues, or view results of an Action run. That's where GitHub CLI comes in. These tools complement each other and not replace each other.

In summary:

• Use gh to create a GitHub repository and add it as a git remote;
• Use git to commit and push, like before;
• Use gh to create and list GitHub issues, etc.

[CQUPTLei]

Okay，I have got it. Thanks a lot!

[xparq]

If not, what are the advantages of using gh?

GitHub CLI is a tool to interface with GitHub-specific features. GitHub is built around the concepts of Git repositories and adds extra features on top:

Well, there appears to be quite a huge overlap with Git in the gh repo command anyway, even in closely related basic functionality like create, clone, even pull (via sync -- which I'd assume (without messing with it first) could also do a push then, too, if parametrized accordingly).

So, for an intuitive interface, gh repo push should also be there, or at the very least sync should be extended to cover that (or at least tell something about the asymmetry of having pull, but not push).

[Krahos]

If not, what are the advantages of using gh?

GitHub CLI is a tool to interface with GitHub-specific features. GitHub is built around the concepts of Git repositories and adds extra features on top:

Well, there appears to be quite a huge overlap with Git in the gh repo command anyway, even in closely related basic functionality like create, clone, even pull (via sync -- which I'd assume (without messing with it first) could also do a push then, too, if parametrized accordingly).

So, for an intuitive interface, gh repo push should also be there, or at the very least sync should be extended to cover that (or at least tell something about the asymmetry of having pull, but not push).

In my opinion it should be there. I just created a PR from a local branch which was automatically pushed. Then I started looking for a way to update the PR through gh instead of git push and found out the command doesn't exist.
But anyway the functionality is already there, only the CLI command is missing and it would be much more intuitive to have it.

[vishalgakhare]

should this be logged as an issue?