Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git push --force-with-lease example-branch without repository fails #15577

Closed
1 task done
tsuyo opened this issue Feb 17, 2022 · 1 comment · Fixed by #15535
Closed
1 task done

git push --force-with-lease example-branch without repository fails #15577

tsuyo opened this issue Feb 17, 2022 · 1 comment · Fixed by #15535
Assignees
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@tsuyo
Copy link
Contributor

tsuyo commented Feb 17, 2022

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message

What part(s) of the article would you like to see updated?

The issue:
On the document page, there are 2 git push commands mentioned as git push --force-with-lease example-branch and git push --force example-branch. But neither of them will not be successful without a repository name before a branch name.

What is the expected outcome?
these git push commands should be git push --force-with-lease origin example-branch and git push --force origin example-branch respectively.

Additional information

No response

@tsuyo tsuyo added the content This issue or pull request belongs to the Docs Content team label Feb 17, 2022
@welcome
Copy link

welcome bot commented Feb 17, 2022

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Feb 17, 2022
@ramyaparimi ramyaparimi removed the triage Do not begin working on this issue until triaged by the team label Feb 18, 2022
@vgrl vgrl self-assigned this Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants