Just to follow up on this.. for ORM I went ahead and protected master, 5.0,
4.3 and 4.2 branches.
On Tue, Nov 24, 2015 at 10:33 AM Steve Ebersole wrote:
> This has always made me nervous ever since it happened a few times
> inadvertently after first moving to git. Thanks for pointing out that
This has always made me nervous ever since it happened a few times
inadvertently after first moving to git. Thanks for pointing out that
they finally added support for that.
For reference...
https://github.com/blog/2051-protected-branches-and-required-status-checks
On Tue, Nov 24, 2015, 10:24 A
+1
On 24 November 2015 at 15:58, Sanne Grinovero wrote:
> Hi all,
> GitHub now provides an option to:
> - prevent pushing with the "force" option to a specific branch
> - prevent people to delete a specific branch
>
> Considering our workflow and also to prevent user mistakes, I think we
> sho
Hi all,
GitHub now provides an option to:
- prevent pushing with the "force" option to a specific branch
- prevent people to delete a specific branch
Considering our workflow and also to prevent user mistakes, I think we
should enable them on the reference repositories (the ones in
github.com/hi
