Help Center>
CodeArts Repo>
FAQs>
Troubleshooting>
Message "fatal: refusing to merge unrelated histories" Is Displayed
Updated on 2023-12-04 GMT+08:00
Message "fatal: refusing to merge unrelated histories" Is Displayed
Symptom
The message refusing to merge unrelated histories is displayed after git pull is executed.
Analysis
The objects of the merge attempt are two unrelated repositories or branches.
Solution
Run git pull origin master --allow-unrelated-histories for force merge.
Parent topic: Troubleshooting
Troubleshooting FAQs
- Private Key Is Lost
- SSH Key Already Exits
- Git Keeps Asking for Passphrase During Code Clone via SSH
- Password Incorrect During Code Clone via HTTPS
- Committed Files Cannot Be Found in the Cloud Repository
- Message "pathspec XXX did not match any files" Is Displayed
- Message "Transport Error: cannot get remote repository refs. XXX.git: cannot open git-upload-pack" Is Displayed
- Message "syntax error near unexpected token `newline'" Is Displayed
- Message "unable to auto-detect email address" Is Displayed
- Message "fatal:Authentication failed" Is Displayed
- Message "'origin' does not appear to be a git repository" Is Displayed
- Message "You are not allowed to push code to protected branches on this project" is Displayed
- Message "Not a git repository" Is Displayed
- Message "src refspec master does not match any" Is Displayed
- Message "destination path 'XXX' already exists and is not an empty directory" Is Displayed
- Message "The requested URL returned error: 401" Is Displayed
- Code Push Fails
- Code Pull Fails
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- Message "SSL certificate problem" Is Displayed
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
more
