[chef-dev] Disabling force push to master for Opscode repos


Chronological Thread 
  • From: Tyler Ball < >
  • To:
  • Subject: [chef-dev] Disabling force push to master for Opscode repos
  • Date: Wed, 10 Dec 2014 08:33:21 -0800

As a response to the recent force push post mortem we had I have had Github disable force pushing to the default branch across all Opscode repos.  So if you are trying to force push and you see a message like:

Counting objects: 8, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 275 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: error: GH003: Sorry, force-pushing to master is not allowed.
To :opscode/client-docs.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to ' :opscode/client-docs.git’

That means your push to master was rejected!  Try rebasing or merging master to your branch.

More details available at the blog post: https://www.chef.io/blog/2014/12/08/chef-client-repo-force-push-to-master-post-mortem-followup/


Thanks!
-T


  • [chef-dev] Disabling force push to master for Opscode repos, Tyler Ball, 12/10/2014

Archive powered by MHonArc 2.6.16.

§