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
Hi Steve,
thanks for the feedback. In doubt, I've released HCANN 5.0.1.Final
without that PR for now.
Thanks,
Sanne
On 23 November 2015 at 19:16, Steve Ebersole wrote:
> As far as the #7 PR, corry I personally have no idea. The problem is all
> the "other" consumers of HCANN I am always told ab
Hi all,
Hibernate Commons Annotations 5.0.1.Final is now available in JBoss's
Nexus, and will soon be available via the Maven Central mirros.
Compared to 5.0.0.Final, only one difference:
https://hibernate.atlassian.net/browse/HCANN-74
That's a little performance improvement.
N.B. :
it's back
Hello, yes, you are absolutely right, the main concern here is that with
new MultipleLoad API we got inconsistent behavior for loading using
IdentifierLoadAccessImpl and MultiIdentifierLoadAccessImpl.
What regarding my case, it is loading data from EAV model, with predefined
scenarios.
We have
