When creating a new repo -- the instructions state to checkout the main branch with git checkout -b main
while a further instruction states to push your changes with git push -i origin master
Those two branches should obviously be consistent with one another
I suspect ./doc/development.rst should be updated as well -- but I'll let you guys sort that one out.
You don't actually need to give a branch name to git push -u unless you want to change the name, as it defaults to the name of the current branch. So the simplest solution might be to just avoid the whole question with e.g.:
git push -u
touch README.rst git add README.rst git commit -m "Add README file" git push -u origin
(Edit: That's assuming push.default is set to simple in the git config, which is the default since Git 2.0.)
push.default
simple
Metadata Update from @wombelix: - Pull-request tagged with: pkgs.fp
This project has moved to https://forge.fedoraproject.org/apps/pagure. As part of the migration, all open pull requests on pagure.io have been closed. If you'd like to continue working on this, please fork the repository on the new forge and re-submit your PR there.
Pull-Request has been closed by ryanlerch
When creating a new repo -- the instructions state to
checkout the main branch with
git checkout -b main
while a further instruction states to push your changes with
git push -i origin master
Those two branches should obviously be consistent with one another