-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Move unpublished commits on master to new branch #1021
Comments
I need this. |
We've discussed various ways of addressing this in the past and I think it's a really interesting area for improvement. I think at the very least we should show a warning when committing straight to master with the option of creating a branch. We've also discussed supporting the scenario you describe of being able to bring commits out of master and resetting it to the origin branch. That path has a whole lot of edge-cases though so I'd really prefer it if we could prevent these "accidents" from happening in the first place. That said I think we're pretty full for beta and possibly 1.0 as well but this is a great feature that I want for us to get in at some point. |
I still want to call this feature "New Branch, Maybe?" and ensure it's pronounced like "Call Me, Maybe?", but this came up at our mini-summit and is an idea we want to revisit. Stay tuned for more details. |
Just want to call out that there are a couple use cases here to potentially differentiate:
|
I'm going to roll #3633 into this issue, as I think there's an opportunity to take a more holistic look at branch protections and understanding people's workflows there. |
Closing this issue in favor of #7023. |
Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 1 to 2. - [Release notes](https://github.com/softprops/action-gh-release/releases) - [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md) - [Commits](softprops/action-gh-release@v1...v2) --- updated-dependencies: - dependency-name: softprops/action-gh-release dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I cannot remember to create a branch first before I start making commits on master. I'll get halfway through whatever edits and I'm like "d'oh! I forgot a branch" so I can either try to remember my cheatsheet list of git commands to get my changes back to a branch, or what I honestly do is ctrl-c, ctrl-v, do a reset --hard, and then (if I'm lucky) create the branch, and then put my changes back.
What I want is something that will take whatever commits I have locally and move those commits to a new branch and leave the remote untouched.
The text was updated successfully, but these errors were encountered: