[
https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin...
]
Michael Biarnes Kiefer commented on DROOLS-656:
-----------------------------------------------
yeah -
i tried with a rep I will remove right now.
I tried from two sides - local as mbiarnes and on the server as kiereleaseuser.
kiereleaseuser modified some files and commited and pushed them.
mbiarnes modified the same files and tried ti do a git push -f origin master and get:
Counting objects: 17, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (12/12), done.
Writing objects: 100% (17/17), 5.12 KiB | 0 bytes/s, done.
Total 17 (delta 1), reused 3 (delta 0)
remote: error: GH003: Sorry, force-pushing to master is not allowed.
To git@github.com:droolsjbpm/testRepo.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@github.com:droolsjbpm/testRepo.git'
I will close this JIRA then
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)