Hi, you cannot commit nor push using GitHub CLI.

If you look at gh help, you will see commands related to GitHub Issues, Pull Requests, Releases, and so on. But there are no commands to make commits. This is because GItHub CLI does not replace git.

To commit and push, you can use git on the command-line:

$ git add myfile1.txt myfile2.txt
$ git commit -m "My commit message"
$ git push -u origin HEAD

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.

Step-1:

Download git from here

Step-2:

Create a repository in github

Step-3:

goto your project folder

step-4

open git bash or cmd and initialize your project by typing git init

step-5

add files by typing git add . for adding all file

step-6

commit your project by typing git commit -m 'your message'

step-7

copy your remote location from github by typing

git remote add origin 'your repository link'

step-8

push your code in github by typing git push -u origin master

and thats all you need to do. Or check github documentation.

I'm sorry you're having trouble!

1. Can you confirm that you are running a recent version of gh?
2. After running git push, can you confirm that a same-named branch was pushed to a remote and that its git commit SHA matches the latest commit on your local branch? git branch -rv | grep -F "$(git branch --show-current)"
3. If you're pushing to a remote branch of a different name, can you confirm that you current branch has upstream configuration? git config -l | grep -F "$(git branch --show-current)"