Git error when trying to click - reject before receiving

Question

When I try to push the change I made, 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 happening?

Answer 1

You should ask who will support the repo at git@mycogit/cit_pplus.git .

Your commits were rejected by the pre-receive hook of this repo (that a user-customizable script designed to analyze incoming comments and decides how good they are for acceptance in the repo).

It’s also nice to ask a person to update the hook so that they print the reasons for the rejection.

If the developer is you yourself, then it looks like you are having a problem with server-side configuration. Please share more information.

Answer 2

I bet you are trying to not push forward, and the hook blocks it. If so, just run git pull --rebase before clicking to restore local changes to the newest codebase.

Answer 3

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

The pre-receipt hook was rejected as a result of a large file. Mostly push validation.

To solve this problem, I deleted the last commit using:

 git reset --soft HEAD~1 

Then I excluded the file from the commit.

Note: Use HEAD ~ N to revert to N the number of previous commits. (i.e. 3, 4) Always use the --soft switch to save changes to the folder

Hope it helps.

Answer 4

This may be due to the fact that you did not have access rights to send a commit to a branch, for example, master . You can ask the attendant to give you the right to push commits.

Answer 5

In my case, I received this message because the branch was marked as “Protected” in GitLab.

Answer 6

I had this problem when trying to merge changes with a file size larger than the remote repository is allowed (in my case it was GitHub)

Answer 7

I received this message when the GitLab server underwent some changes. The next day the push worked perfectly. In any case, as others have indicated, consult with your attendant.

Answer 8

I ran into the same problem.
For me, it decided to switch to another branch and then return to the original one.

Not sure if there was a reason for the underline, but this fixed it.

Answer 9

This actually happens when YACC is enabled on the server side in BitBucket. YACC allows you to specify JIRA problem names in a commit message. Therefore, whenever you do something, save your JIRA number in the commit message, and then in addition you can add your own message.

Answer 10

I used GitKraken and we created a local branch, then we merged the two remote branches in it, and then we tried to push the local branch to the source. It did not work with the same error message.

The solution was to create a local branch and push it first to the source, and then merge.

Answer 11

Problem: "PUSH Failed refs / head / - pre-receipt hook rejected"

I ran into the problem of the inability to transfer my changes to my source branch and anything to the main branch of the repository of a specific project, since the size of this repo exceeded the hard limit of 2 GB. It was a mistake. This is because we unknowingly placed test data in bitbucket from other branches of testing.

PUSH Failure refs / head / - pre-hook rejected

So, the verification attempt is that the same thing with another project repository, and they had no problems.

Fix:

My colleague noticed that when we cloned the project locally, the project size was 110 MB. So, we started clearing previously merged branches and active branches that are no longer required. As soon as this cleaning was done for several branches, we realized that the repo size sharply decreased from 2 GB to 120 MB. Then we tried to push the changes to my branch, and it worked.

Answer 12

If this helps someone:

I had an empty repository without the main branch for unprotecting (in Gitlab), so before running git push -u origin --all

• git push -u origin master I had to run git push -u origin master ,
• temporarily remove protection from the main branch
• push the rest ( --all and --tags )

Answer 13

I got this while trying to click on a dokku instance. It turns out that the disk was full on my server.

Ran: du -f

And the 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 14

In my case, we have hooks for commit messages, our server-side script accepts commits if they have a special format for the commit message "<JIRA ID><Message>" . He (catches) rejects the commit if the corresponding Jira ticket does not exist or if there are special characters in the commit message. I encounter this error when I add /, [,> etc. In the commit message, deleting these works fine.

Answer 15

For me, authorization on a remote git server will solve the problem.

Answer 16

In my case, this is because I accidentally added a giant file to my uncommitted push, and I could not get rid of it, no matter what press or reset or rm I did after.

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

It doesn’t sound very good, but it works ...

Answer 17

The mistake for me was that not a single branch was created in the project, and my role was the developer, so I could not create any branch, demand that they give me the appropriate permissions and everything is fine now!

Answer 18

bastard --rebase

Worked for me. thank

Answer 19

Bitbucket : check for permissions for the branches in the settings (this could be "Deny All"). If this does not work, just clone your branch to a new local branch , transfer the changes to the remote one (a new remote branch will be created) and create a PR.

Answer 20

I encountered the same error, after checking, I had developer access and I could not publish a new branch. Adding higher permissions solved this problem. (Gitlab)

Answer 21

Specifying the version of node.js can solve the problem as follows

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