`push to current branch` not working for main branch

[Shah-Saumya]

• I attempted to commit all the code to the main branch without creating a pull request, but instead, a new branch was created.

[siddharthkp]

This definitely looks like a bug! Thanks for taking the time to report it, going to create an internal tracking issue for this as well!

(Tracking issue for github staff: https://github.com/github/copilot-workspace/issues/330)

[Raushang4]

> * I attempted to commit all the code to the main branch without creating a pull request, but instead, a new branch was created.

Understanding the Situation
Branch Creation:
When you create a new branch (e.g., using git checkout -b new-branch), you switch your working context to that branch. Any commits made afterward will go to this new branch, not the main branch.
Direct Commit vs. Pull Request:
Committing directly to the main branch means bypassing the pull request (PR) workflow, which is often used for code review and collaboration. If your repository settings do not enforce PRs, you can push directly to the main branch.

To commit your changes directly to the main branch, follow these steps:

Switch back to main branch: git checkout main 🛠️
Merge changes from new branch: If you want to incorporate changes from "new-branch", use git merge new-branch 🔄
Commit your changes: If there are uncommitted changes, add and commit them using git add . and git commit -m "Your commit message" 📝
Push changes to remote repository: Finally, push your changes using git push origin main 🚀

[dylanatsmith]

This is still ongoing. Should we remove the push options from the menu since they don’t function properly? At least until we have a fix?