4 ms·
> Everything I've seen or heard of is PullRequests, code-review, +1, then merge to master. That won't help you when you think you're pushing to and from your o
by yawaramin 11y ago
> Everything I've seen or heard of is PullRequests, code-review, +1, then merge to master.
That won't help you when you think you're pushing to and from your own branch, but are accidentally on develop and force-pushing to the remote develop branch.
- detaro 11y agoBut if your process is only merging PRs, then locking the master against pushes as he proposes would create no further issues, preventing that from happening. If you need to modify the master directly, it would complicate things.
- deleted 11y ago[deleted]
- matwood 11y agoThat's where locking down the branches and preventing rebases comes into play. It prevents someone from accidentally doing what you describe. Most people only know github and I don't think they expose this locking feature in their UI which is a shame.