First, make sure that you did push to the right branch and that the commit still doesn’t show up in the PR. For me, the commit showed up when I viewed the specific branch in the repo, but didn’t show in the PR and didn’t trigger CI. This is what fixed the issue for me: … Read more
git push can push all branches or a single one dependent on this configuration: Push all branches git config –global push.default matching It will push all the branches to the remote branch and would merge them. If you don’t want to push all branches, you can push the current branch if you fully specify its … Read more
I had the same problem but this command resolved it. Replace: git push -u origin master with following command: git push -u origin main or git push -f origin main
You are actually asking two questions: in the title – how to pull without merge (I came here for this question, originally;) in the description – how to check out a branch without merging in to master Pull remote branch without merge # Assuming you are on wanted branch (b1) already git pull –rebase No … Read more
When you pulled the branch, did you use the “–track” option (in order to keep you local branch tracking the remote branch). If you did not, it can explain that the “merge” command that does not work. You can do the merge manually: git fetch git merge origin/groups To compare local and remote repos, I … Read more
if you are using Windows, you can try the following steps: look for your ssh public key usually you can find it at c:\\users\\YOUR_USERNAME\\.ssh copy your openshift public key to your git’s ssh-key folder suppose we have git in d:\\git then we need to copy the public key from c:\\users\\YOUR_USERNAME\\.ssh to d:\\git\\.ssh try if it … Read more
Ok I got the answer from IRC after a long chat. I’ll have to work with forks and pull requests, or add pre-push hooks on each dev’s machine since GitHub doesn’t allow per branch permissions neither pre-publish canceling hooks. Here is a part of the answers I got: Fork the repository. then the developer can … Read more
Actually, I think I like my comment enough to post it as an answer! When you push, git creates a pack of all the necessary objects and uploads that to the remote. This means we’re looking for a way to predict that pack size. Since the packs are compressed, that makes it very difficult to … Read more
When you did a git-pull, modifications from the remote branch were merged into your local branch. The automatically generated commit signifies that. Merging could have resulted in conflicts, which would then need to be resolved manually. In your particular case, this did not happen and git could take care of everything.
This error message: error: remote unpack failed: unable to create temporary object directory indicates that the Git repository at the server (not your Git) is out of space, or running into similar server problems,1 or installed incorrectly. That is, given: To: http://git.int.censoredlink/scm/freeb/freebrep.git you will have to log in to the machine that serves HTTP traffic … Read more