Error on git push = ! [remote rejected] master -> master (pre-receive hook declined)

Asked 28/1, 2014 at 14:15 Answered 10/8, 2023 at 14:18

I think, it's a different issue than this(remote rejected master -> master (pre-receive hook declined)), and many people are facing the same issue, So I am posting a new here.

My friend added me on bitbucket.org as an admin, so that I can help on his project. So, I wanted to start by taking a pull of the latest code on my local.

Steps I followed:

Goto empty folder
git init
git remote -v (this gives nothing)
git remote add origin <path to git repo>
git remote add master <path to git repo>
git remote -v (this show both with fetch and push in brackets)
git fetch origin master
git pull origin master (I have latest code now, all files and folders)
touch test (lets test a "test" commit)
git status
git add .
git commit -m "testing, first commit"
git push origin master

error:

Counting objects: 4, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 274 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: permission denied to update branch master
To '<repo path>'
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '<repo path>'

Ugrian answered 28/1, 2014 at 14:15 Comment(0)

It looks like the branch management (one of the admin settings) in bitbucket has been configured to only allow certain people to push directly to master.

Try creating a branch - git checkout -b test, create your test commit and push git push origin test:test. You can always cleanly delete this branch once you have completed the test.

The other option (probably best agreeing with whoever set this up) is you go to bitbucket and head to admin, branch management and remove master be too limited. cf - https://confluence.atlassian.com/display/BITBUCKET/Branch+management

Ocelot answered 28/1, 2014 at 15:59 Comment(5)

I didnt add myself for push to branch. Thanks the other option worked for me. – Ugrian 29/1, 2014 at 6:39

Just add permission throught bitbucket WORked FOr Me – Struve 7/10, 2016 at 16:42

for me below command worked, git commit --amend --reset-author and then use git config user.email "[email protected]" git config user.name "Kadam, Somnath" and now git push origin master – Insatiable 20/6, 2018 at 9:37

Same error came to me for another branch. I had set "Write access" to "Nobody" in "branch permissions". Making it to "Everybody" resolved the issue for me. – Poker 24/11, 2021 at 6:43

In my case, I was a repository administrator. I was having the same problem until I added my individual account as having Write access to the branch. The Administrators group had Write access, but I hadn't been added there. After the main admin added me to the group, I didn't need the individual account. It sucks that I can mangle the repository configuration as an administrator multiple ways but I couldn't push source code changes as one. – Lecturer 20/7, 2022 at 15:31

Just reporting another case leading to the specified error. If the Bitbucket repository size reaches 2 GB, Bitbucket itself restricts the repository to read-only access. When that happens, contributors with read/write permissions are not able to push and get the "pre-receive hook declined" error.

I also found these documents from Atlassian: https://blog.bitbucket.org/2014/05/30/repository-size-limits/ https://confluence.atlassian.com/bitbucket/reduce-repository-size-321848262.html

Links include a guide on how to restore the repo back to full functionality

Callis answered 18/10, 2017 at 8:23 Comment(0)

I have a better solution on Bitbucket: If you are admin go to Repo >Settings >Limit Pushes section, and in "Branch name" put 'master', and in "..search... user" put your user name - then push "ADD" - and you are done :)

Pashto answered 5/4, 2016 at 18:31 Comment(0)

I think package setuptools/distribute is listed in requirements.txt. Please remove the same.

Lotion answered 1/12, 2014 at 5:16 Comment(0)

The same issue with me on gitlab, I asked the repo owner to grand me maintainer role and the issue fixed.

Euroclydon answered 9/4, 2019 at 8:48 Comment(0)

Another scenario -> I also had this issue and I also configured global parameters, tried branching etc but it didnt work for me.

Below was the issue -> I recently joined my current firm and till my Bitbucket credentials got activated, I was using someone elses credentials to access Jira, Bitbucket etc. Now this credetials got saved in Windows inside "Credential Manager". After deleting those other colleague credentials, it worked fine for me.

Latex answered 23/11, 2021 at 8:57 Comment(0)

I wanted to force push on my ticket branch, and it was rejected. Went to Repository settings -> Hooks -> found out that Reject Force Push was enabled, and disabled it.
Use at your own risk.

Mesothorax answered 10/8, 2023 at 14:18 Comment(0)

-2

What worked for me was:

Created a new branch locally
Bitbucket -> Settings -> Repository details = changed default branch (e.g to prod)
Bitbucket -> Branches -> delete master branch (you can do this without step 2)
Then push your locally created branch (e.g master)
Bitbucket -> Settings -> Repository details = changed default branch (e.g to master)

Phyllida answered 2/12, 2015 at 8:17 Comment(0)

Recommended topics

Hot tags