[
https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin...
]
Geoffrey De Smet edited comment on DROOLS-656 at 3/6/15 2:34 AM:
-----------------------------------------------------------------
Yes, James Dennes (Github Staff) told me it's done on all repo's of
https://github.com/droolsjbpm on all branches (but not forks of course) on 20-JAN-2015.
No idea if it automatically applies to new repo's in that same github organization...
was (Author: ge0ffrey):
Yes, James Dennes told me it's done on all repo's of
https://github.com/droolsjbpm
on all branches (but not forks of course) on 20-JAN-2015.
No idea if it automatically applies to new repo's in that same github organization...
The blessed repo's should not accept a git force push
-----------------------------------------------------
Key: DROOLS-656
URL:
https://issues.jboss.org/browse/DROOLS-656
Project: Drools
Issue Type: Task
Reporter: Geoffrey De Smet
Assignee: Michael Biarnes Kiefer
Priority: Critical
If someone ever git forces pushes to a blessed repo all hell will break loose.
We can prevent git forces pushes, as explained here:
http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi...
Force pushing on blessed repo's is very bad, but force pushing on forks is very
common.
Requirements:
- Enable this on 1 new dummy blessed repository
- Prove you cannot force push to
- Prove you can fork it and force push to your fork.
- Delete the dummy blessed repository
- If that works well, enable it on the real blessed repositories
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)