尝试推送时出现 Git 错误 -- 预接收挂钩被拒绝

Question

When I try and push a change I've commited, I get the following error...

git.exe push -v --progress  "origin" iteration1:iteration1

remote: *********************************************************************
To ssh://git@mycogit/cit_pplus.git
! [remote rejected] iteration1 -> iteration1 (pre-receive hook declined)
error: failed to push some refs to 'ssh://git@mycogit/cit_pplus.git'

What's going on?

Answer 1

You should ask whoever maintains the repo at git@mycogit/cit_pplus.git .

Your commits were rejected by the pre-receive hook of that repo (that's a user-configurable script that is intended to analyze incoming commits and decide if they are good enough to be accepted into the repo).

It is also a good idea to ask that person to update the hook, so it would print the reasons for the rejection.

If the maintainer is you yourself, then it looks like you've got a problem with your setup on the server-side. Please share more information then.

Answer 2

I'd bet that you are trying a non-fast-forward push and the hook blocks it. If that's the case, simply run git pull --rebase before pushing to rebase your local changes on the newest codebase.

Answer 3

File size is important. There is a limit of ~120MB for a single file. In my case, .gitignore using Visual Studio had the file listed, but the file was still committed. When using the git cli, we can get more detail information about the error.

pre-receive hook declined was as a result of the big file. Basically validating the push.

To resolve it, I removed the last commit using:

git reset --soft HEAD~1

I then excluded the file from the commit.

Note: Use HEAD~N to go back to N number of previous commits. (ie 3, 4) Always use the --soft switch to maintain changes in the folder

hope it helps.

Answer 4

就我而言，我收到此消息是因为该分支在 GitLab 中被标记为“受保护”。

Answer 5

This may be because you didn't have the access right to push a commit to a branch such as master . You can ask the maintainer to give you the right to push commits.

Answer 6

in sometimes, because the branch you are pushing has been protected, so you can ask the repository's maintainers to change the protecting status. in git-lab , you can find it in

Settings > Repository > Protected Branches .

:)

Answer 7

On my case (Bitbucket), the problem was Rewriting branch history is not allowed restriction. Go to Repository settings -> Branch Permissions edit the selected branch's permissions, and check Allow rewriting branch history

Answer 8

I got this message when the GitLab server was undergoing some changes. The next day pushing worked fine. Anyways, as others pointed out, check with your maintainer to be sure.

Answer 9

I encountered this same issue.
What solved it for me was to switch to another branch and then back to the original one.

Not sure what the underline cause was, but this fixed it.

Answer 10

尝试合并文件大小大于远程存储库允许的更改时遇到此问题（在我的情况下是 GitHub）

Answer 11

In case it helps someone :

I had a blank repo with no master branch to unprotect (in Gitlab) so before running git push -u origin --all

• I had to run git push -u origin master first,
• unprotect the master branch temporarily
• push the rest ( --all & --tags )

Answer 12

Bitbucket : Check for Branch permissions in Settings (it may be on 'Deny all'). If that doesn't work, simply clone your branch to a new local branch , push the changes to the remote (a new remote branch will be created), and create a PR.

Answer 13

I faced the same error, upon checking I had a developer access and couldn't publish a new branch. Adding higher access rights resolved this issue.(Gitlab)

Answer 14

I got this error with GitHub gist. I was trying to push a commit with files in sub-directories. Turned out gist can only have files in root directory.

Answer 15

删除受保护的分支选项或允许其他角色（如开发人员或管理员）允许这些遇到此错误的用户进行合并和推送。

Answer 16

In my case, we have hooks for commit messages, our server script accepts commits if they have the special format for commit message "<JIRA ID><Message>" . It(hook) declines commit if respective Jira ticket does not exist or there are some special symbols in the commit message. I face this error when I add /, [, > etc. in a commit message, removing those works fine.

Answer 17

For me Authorization on remote git server solve the problem.

Answer 18

I was using GitKraken and we made a local branch, then we merged two remote branches in it and then we tried to push the local branch to origin. It didn't work with the same error message.

The solution was to create the local branch and push it first to origin and then do the merge.

Answer 19

In my case I got this error because a branch with the same name already existed. Deleting this branch off of the git server will fix this.

Answer 20

我通过重新生成 SSH 密钥并将其添加到 GitHub 帐户解决了这个问题。

Answer 21

I got this when trying to push to a dokku instance. Turns out the disk was full on my server.

Ran: du -f

And result was:

Filesystem      Size  Used Avail Use% Mounted on
udev            476M     0  476M   0% /dev
tmpfs           100M  4.4M   95M   5% /run
/dev/xvda1      7.8G  7.4G  8.9M 100% /

Answer 22

This is actually happens when YACC is enabled at server side in BitBucket. YACC is enable for JIRA issue names to be mentioned in the commit message. So whenever you commit anything atleast keep your JIRA number into the commit message and then additionally you can add your own message.

Answer 23

Issue: "PUSH Failed refs/head/ - pre-receive hook declined"

I've faced the problem of unable to push my changes to my origin branch and anything to master branch of a particular project repository as the size of that repo was over hard limit of 2GB. It was throwing the error. That's because we had pushed the test data unknowingly to bitbucket from other testing branches.

PUSH Failed refs/head/ - pre-receive hook declined

So tried checking is that the same with other project repo's and they weren't having any issues.

Fix:

My colleague noticed that when we cloned the project back locally, the size of the project was 110MB. So then we started cleaning the branches we merged earlier and active branches which are no more required. Once that cleaning is done for couple of branches we realized the size of the repo went drastically down from 2GB to 120MB. Then we tried to push the changes to my branch and it worked.

Answer 24

对我来说，错误是该项目没有创建任何分支，而我的角色是开发人员，所以我无法创建任何分支，请求他们给我相关的权限，并且现在一切都井井有条！

Answer 25

A default branch (eg master ) does not yet exist for your remote. So you first need to create master branch in the git remote server (eg creating a default README.md file) then try to push all your existing local branches using this command:

git push -u origin --all

Answer 26

In my case I had a new repository, pushed a branch ('UCA-46', not 'master'), rebased it, forcely pushed again and got the error. No web-hooks existed. I executed git pull --rebase as @ThiefMaster advised, had to rebase again and was able to push the branch. But that was a strange and difficult way.

Then I saw Git push error pre-receive hook declined . I found that my branch became protected . I removed protection and could forcely push again.

Answer 27

I got this message while trying to delete a remote branch (git push origin --delete [branch-name]). The problem was that the branch was marked un-deletable in bitbucket.

Answer 28

Your commit is not compatible with the repository maintainer's rules, you just need to git reset --hard HEAD ~ 1 in order to delete the last commit. After that commitment according to the maintainer's rules is ok

Answer 29

In my case there was a Committer restriction in a project on Gitlab:

Users can only push commits to this repository that were committed with one of their own verified emails.

Since I also configured SSH on my machine, my global_user_email was updated in the git config file with my machine's address, hence the remote was not allowing to push.

You can find this at:

• Gitlab -> Settings -> Repository -> Push Rules

Just disable the commit restriction and it will work.

Answer 30

This is a rather old question and has many answers already. But I would like to share the solution that worked for me while working with bitbucket (no admin rights). Most of my colleagues (to the exception of one) did not face any issues. The both of us could suddenly not push to precise branches any longer (I could not figure out the actual reason). The solution was:

1. delete existing pull requests related to the problematic branches,
2. delete the branches on server side,
3. re-push from local to remote repo, and,
4. create the pull request again.

Answer 31

I had a similar issue and it was caused by bcrypt npm package. I uninstalled bcrypt and instead installed bcryptjs.

npm install --save bcryptjs && npm uninstall --save bcrypt

It's the exact same API. All the code inside app.js remains same except the require call need to be changed to require("bcryptjs");

Answer 32

I got the same error ! [remote rejected] ... (pre-receive hook declined) ! [remote rejected] ... (pre-receive hook declined) today.

It was caused by Bitbucket having a problem . So make sure that your Git Remote is up and running.

The issue that prevented me from pushing was: https://bitbucket.status.atlassian.com/incidents/r8kyb5w606g5

Answer 33

If in a corporate gitlab/ github and you trying to push changes to a branch/master, Pre-hook could mean that you missed some parameters input into the commit message.

In my case, along with message i was needed to add bug id, bug url and approver in commit file and then push to branch and place the merge request.

Hope this helps, as when writing commit message ask your mentor/buddy for th e requirements in a commit message.

Answer 34

Simple and Quick fix:-

git commit -m "branch_name:added git script"

Answer 35

! [remote rejected] master -> master (pre-receive hook declined)

I spend 2 days on this bug! After a lot of research, I finally found a solution for this.

1. Heroku config:set USE_NPM_INSTALL=false
2. Configured the yarn build pack on Heroku
3. Make sure yarn.lock file is NOT in your .gitignore file

It will work!

Answer 36

In my case I manage the project myself but recently upgraded it to the hobbyist tier. In any case checked the logs through herokus browser interface and it had a very clear message about the node version (its an express app) not being defined in the package.json. They had a link to a heroku page outlining how to fix it and it worked.

In any case I just added this to my package.json and no further issues!

  "engines": {
    "node": "16.x",
    "npm": "6.x"
  },

I checked my node version and npm versions first though just to be clear. My node version was 16 but my npm version was 7. I decided to leave the npm defined as 6.x just because it's what was listed on the heroku page. Didn't encounter any issues.

$ node --version

$ npm --version

And here's the link to the heroku help page for this.

https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version

Answer 37

My issue was file size, trying to migrate a project from gitlab to github, and the error did hint at it for me, directing to this page https://docs.github.com/en/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage

The command used was:

git lfs migrate import --everything --above=100kb

After this I was able to git push --mirror http:...

Answer 38

Step1:

git pull --rebase

Step2:

git reset --soft HEAD~1

Step3:

git commit -m "your comments here"

Step4:

git push

This should fix your issue.

Answer 39

In my case, it was jira issue integration under project settings in BITBUCKET. By means, we need to put jira issue associated with it. I had two options 1) disable jira issue in the commit 2) put jira issue reference to the commit.

Answer 40

In my case, it's because I accidentally added a giant file to my uncommitted push and I could not get rid of it no matter whatever pull or reset or rm I did after.

my dirty solution but workable solution is to rename the current directory, re-clone the directory to local and reflect the changes manually to the recloned local directory...

It does not sound good but works...

Answer 41

For me everything was working fine until Bitbucket automatically changed their policy today (April 21, 2020). This happens to align with a new feature recently introduced today called Workspaces , so I suspect it has something to do with that.

Workaround : I (as an Admin) followed the instructions to add the email address to Users in the UI (the email you are using can be found git config --list

Answer 42

I had permissions issue, after given the right permissions i was able to push the contents. I was pushing a existing project into a new git repo.

Answer 43

You should look at the logs. I just ran into the same error and realized from the logs it was because I had a yarn.lock and package-lock.json

Answer 44

If you facing an issue related to pre-receive hook declined in git while doing Push. You may have the below reasons:

1. Maybe your DB backup in your project path app_data is exceeded the 100.00 MB limit of Github.
2. Check the size of your file if you using it in your project not exceeded the size limit of 10.00MB or any file.

You can resolve this issue by the below steps:

1. Just do the zip those files and push again git push -u origin develop

Answer 45

Specifying a node.js version can solve the problem like

{
  "name": "myapp",
  "description": "a really cool app",
  "version": "1.0.0",
  "engines": {
    "node": "10.3.0"
  }
}