We’re using Github: FI and we want to have a release branch that is immune from history manipulation / rebasing. Besides establishing a policy, is there a way, with our current setup, to achieve this?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We’re using Github: FI and we want to have a release branch that is immune from history manipulation / rebasing. Besides establishing a policy, is there a way, with our current setup, to achieve this?
I think establishing a policy is the best way. With manually-managed git repos you can use a hook (probably pre-receive) to deny non-fast-forward pushes, but I don’t believe Github:FI exposes server-side hooks. But a policy and public shaming for any violators is probably going to be effective enough. Besides, a hook would prevent you from force-pushing in the rare event that you, the admin, really do need to “fix up” the branch.