Git push error pre-receive hook declined

Question

I have run gitlabhq rails server on virtual machine  following 1-6 steps from this tutorial https   github com gitlabhq gitlab-recipes blob master install centos README md and starts rails server executing command sudo -u git -H bundle exec rails s -e production  After that I created user  using admin tools and created new project under this user  Then I m trying to push the existing project to this repo as always  But in the last step  git push origin master fails with the error       remote rejected  master -  master  pre-receive hook declined    Additional info   1  I haven t activated user  project owner  via email activation link  because I haven t configured post service on server-side and I didn t find instructions how to do that in this manual   2  Gitlab server generates tips how to push project to repo and there is not repositories  in path  I mean it generates git mygitlabhost user repo git instead of git mygitlabhost repositories user repo git which is correct   3  When i tried to debug it  I opened pre-receive script inside repo on server and tried to output variables  there is 3 of them   refs   ARGF read  key id    ENV  GL ID   and repo path   Dir pwd and found  that key id is always empty  Maybe the problem is here    If so  please give me suggestions on how to fix that  Thanks

User · Answer

I solved this issue by changing remote  origin  url from http to git protocol in  git config

User · Answer

ihave followed the instruction of heroku logs img https   devcenter heroku com articles buildpacks detection-failure    use cmd  heroku logs -  show your error   then do the cmd   heroku buildpacks clear   finally  it worked for me

User · Answer

Please check if JIRA status in  quot In Development quot   For me   it was not   when i changed jira status to  quot In Development quot   it worked for me

User · Answer

Go to Project settings --  Hooks --   Under  Pre-receive hooks  Disable cp require issue reference in commits

User · Answer

GitLab by default marks master branch as protected  See part Protecting your code in https   about gitlab com 2014 11 26 keeping-your-code-protected  why   If so in your case  then this can help      Open your project   Settings   Repository and go to  Protected branches   find  master  branch into the list and click  Unprotect  and try again    via https   gitlab com gitlab-com support-forum issues 40  For version 8 11 and above how-to here  https   docs gitlab com ee user project protected branches html restricting-push-and-merge-access-to-certain-users

User · Answer

I ve faced the same issue  this is because I am pushing my code directly in the master branch  and I don t have rights for this  So I push my code in a new branch and after that  I created a pull request to merge with master

User · Answer

Despite the question is specific to gitlab  but similar errors can happen on github  depending how it is set up  usually Github Enterprise   You need to familiarize yourself with the following concepts   pre-receive hooks organization webhooks Webhooks  Webhooks are more commonly understood than other two items  The Pre-receive hooks  are scripts that run on the GitHub Enterprise server to enforce policy  When a push occurs  each script runs in an isolated environment to determine whether the push is accepted or rejected   Organization webhooks  Webhook events are also sent from your repository to your  quot organization webhooks quot   more info  These are set up in your github enterprise  They are specific to the version of the github enterprise  You may have no visibility because of your access limitations  developer  maintainer  admin  etc

User · Answer

You need to add your ssh key to your git account if it throws error then delete previous ssh key and create a new ssh key then add

User · Answer

Seems the problem is with some services  like sidekiq  Running sudo -u git -H bundle exec rake gitlab check RAILS ENV production outputs all the problems with config

User · Answer

Might not be the case  but this was the solution to my  pre-receive hook declined  error   There are some repositories that only allow modifications through Pull Request  This means that you have to    Create a new branch taking as base the branch that you want to push your changes to   Commit and push your changes to the new branch  Open a Pull Request to merge your branch with the original one

User · Answer

I stumbled across the same error using BitBucket  I had a local Git repo I wanted to back up online  so I created a new repository from my BitBucket account  using the web interface    After running git remote add origin git bitbucket org StatMarianne  lt a private repo gt  git  I ran git push origin master to no avail  I typically don t use the -u option with git push because I don t mind typing up the full repo and branch names when pushing and pulling    The error read   remote  You re not allowed to write to this repository  To bitbucket org StatMarianne  lt a private repo gt  git     remote rejected  master - gt  master  pre-receive hook declined  error  failed to push some refs to  git bitbucket org StatMarianne  lt a private repo gt  git    But my local branch did get successfully pushed when I ran git push -u origin master  following strictly BitBucket s instructions    I find it surprising  since -u  --set-upstream  should only  add upstream  tracking  reference     Anyhow

User · Answer

In my case  my team lead to created a repo repo was empty  and assign me as developer so when I pushed to the code directly to master the error I was facing    remote rejected  master - gt  master  pre-receive hook declined  So how it was fixed that he assigned to me as maintainer so I was able to push the code directly to the master

User · Answer

You might not have developer access to the project or master branch  You need dev access to push new work up    New work meaning new branches and commits

User · Answer

Following resolved problem in my local machine    A  First  ensure that you are using the correct log on details to connect to Bitbucket Server  ie  a username password SSH key that belongs to you     B  Then  ensure that the name email address is correctly set in your local Git configuration   Set your local Git configuration  for the account that you are trying to push under  the check asserts that you are the person who committed the files        Note that this is case sensitive  both for name and email address       It is also space sensitive - some company accounts have extra spaces characters in their name eg   Contractor  space space LDN      You must include the same number of spaces in your configuration as on Bitbucket Server    Check this in Notepad if stuck   C  If you were using the wrong account  simply switch your account credentials  username password SSH key  and try pushing again   D  Else  if your local configuration incorrect you will need to amend it      For MAC   open -a TextEdit app    gitconfig  NOTE  You will have to fix up the old commits that you were trying to push    Amend your last commit    gt  git commit --amend --reset-author        lt save and quit the commit file text editor that opens  if Vim then  wq to save and quit gt   Try re-pushing your commits    gt  git push

[gitlab] Git push error pre-receive hook declined

Examples related to gitlab

Examples related to githooks