Cannot publish unbom head что делать
cannot publish unborn head #5057
Comments
AgbajeMike commented Jun 28, 2018
Description
Version
Steps to Reproduce
Expected Behavior
Actual Behavior
Additional Information
The text was updated successfully, but these errors were encountered:
shiftkey commented Jun 28, 2018
@AgbajeMike thanks for reaching out!
We require the template to be filled out on all new issues. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀
steveward commented Jun 28, 2018
@AgbajeMike usually the UNBORN HEAD error happens when you are attempting to publish a branch that has no commits. If that is the case, make an initial commit and then try publishing your branch again. If you have any further issues, please fill out the template so that we can better help you!
shiftkey commented Jul 5, 2018
Closing this out due to inactivity. @AgbajeMike if @steveward’s advice doesn’t help with your situation, you can fill out the template and we can investigate further.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Cannot publish unborn HEAD/Commit failed exit code 128 ‘cannot lock ref ‘HEAD». #7581
Comments
cfandel commented May 20, 2019 •
Description
Although several existing issues seem similar, none actually address my problem.
I am working in an existing repository that I have been committing and pushing changes to successfully for several months. I am the only person contributing. Overnight, I stopped being able to commit, and get the following error message:
My current branch should be ‘master’ but has changed itself to ‘(unknown)’. When I try to change it back, I get the following error message:
I have local changes I want to keep, because I made changes before the error occurred and haven’t been able to commit them.
Version
Steps to Reproduce
Can’t reproduce as this is only happening on one repository and I don’t know what caused it.
The text was updated successfully, but these errors were encountered:
steveward commented May 20, 2019
cfandel commented May 21, 2019 •
Thanks for the quick response!
Here is a screenshot of the results of git fsck in Git Bash (gives same result as in Command Prompt). 
steveward commented May 23, 2019
@cfandel thanks for sharing that output.
If you run into any issues please let me know.
cfandel commented May 24, 2019
Would it be easier for me to just completely delete the repository on GitHub, and create a new one from scratch by uploading my local files?
cfandel commented May 24, 2019
Also, side question: what causes local repositories to be corrupted and how do I avoid it in the future?
steveward commented May 24, 2019
Does the solution you linked to (the answer by Zoey Hewll) preserve the local version or the version stored on GitHub? And to clarify terminology, the version stored on GitHub is called the remote version right?
And to clarify terminology, the version stored on GitHub is called the remote version right?
That’s correct. The term remotes refers to copies of your repository hosted in different locations (on the internet, on a local server, etc.).
Would it be easier for me to just completely delete the repository on GitHub, and create a new one from scratch by uploading my local files?
I wouldn’t recommend doing that since the version on GitHub is not corrupt (GitHub does not allow you to push corrupt objects up to your remote repository). If you have a more recent backup of your repository somewhere else you could use that for recovery as well.
Also, side question: what causes local repositories to be corrupted and how do I avoid it in the future?
Common causes that I have seen are sudden power failures or third-party file syncing services like Dropbox being used as the storage directory for repositories.
«Cannot publish, unborn head» error message
I know there are other questions on here about this issue, but this case is different because it’s not caused by an empty repo folder or anything, and I’ve been pushing changes to this same repo using GitHub desktop for some time. After I type my changes into the summary window, I hit Commit to Master (branch is already set to master, like always). But I get the unborn head issue, along with the alert that my repo’s name is too long. Again, this has never happened, and the name has never been an issue previously. Here’s a screenshot for reference: 
Does anyone know what might be causing this?
2 Answers 2
The error is due to a file in «Desktop/MY REPOS/The-Tech-Academy-C-Sharp-Coding-Projects/AppData/Local/Microsoft/VisualStudio/15.0_8067392e/VTC/» having a name that is too long. The filename looks like it is generated by a tool, not written by you. In fact it looks like the whole «Desktop/MY REPOS/The-Tech-Academy-C-Sharp-Coding-Projects/AppData/Local/Microsoft/» directory is probably not code that you are working on yourself.
In fact, if «AppData» contains only generated files, then you can even ignore just that.
Not the answer you’re looking for? Browse other questions tagged github or ask your own question.
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.12.10.40971
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
cannot publish unborn head #6207
Comments
billyobuya commented Nov 15, 2018
No description provided.
The text was updated successfully, but these errors were encountered:
request-info bot commented Nov 15, 2018
Thanks for reaching out!
We require the template to be filled out with all new issues. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us halfway 😀
billyobuya commented Nov 15, 2018
how can I solve the problem of not publishing unborn head
billygriffin commented Nov 15, 2018
@billyobuya As presented above, in order to understand what’s happening for you, we ask that you fill out the template (you can copy over from https://github.com/desktop/desktop/issues/new?template=bug_report.md if you’d like). This allows us to gather enough information about what’s happening for you to actually help resolve the issue. Thanks for understanding and meeting us halfway! 😄
tierninho commented Nov 16, 2018
@billyobuya usually the UNBORN HEAD error happens when you are attempting to publish a branch that has no commits. If that is the case, make an initial commit and then try publishing your branch again. If you have any further issues, please fill out the template so that we can better help you!
shiftkey commented Nov 23, 2018
Closing this out because an unborn branch cannot be published (because there are no commits to push), and without more information the advice in @tierninho’s last comment is the best workaround.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
cannot publish unborn head
I know there are other questions on here about this issue, but this case is different because it’s not caused by an empty repo folder or anything, and I’ve been pushing changes to this same repo using GitHub desktop for some time. After I type my changes into the summary window, I hit Commit to Master (branch is already set to master, like always). But I get the unborn head issue, along with the alert that my repo’s name is too long. Again, this has never happened, and the name has never been an issue previously. Here’s a screenshot for reference:
Does anyone know what might be causing this?
2 Answers 2
The error is due to a file in «Desktop/MY REPOS/The-Tech-Academy-C-Sharp-Coding-Projects/AppData/Local/Microsoft/VisualStudio/15.0_8067392e/VTC/» having a name that is too long. The filename looks like it is generated by a tool, not written by you. In fact it looks like the whole «Desktop/MY REPOS/The-Tech-Academy-C-Sharp-Coding-Projects/AppData/Local/Microsoft/» directory is probably not code that you are working on yourself.
In fact, if «AppData» contains only generated files, then you can even ignore just that.
Not the answer you’re looking for? Browse other questions tagged github or ask your own question.
Related
Hot Network Questions
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2019 Stack Exchange Inc; user contributions licensed under cc by-sa 4.0 with attribution required. rev 2019.11.15.35459
Cannot publish a bootstrap website from my local computer through github desktop. It’s states: cannont publish unborn head. What does it mean? What changes should I do?
1 Answer 1
The reason is that your repository is empty and you should make atleast a readme file. It worked in case of mine.
Not the answer you’re looking for? Browse other questions tagged github or ask your own question.
Related
Hot Network Questions
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2019 Stack Exchange Inc; user contributions licensed under cc by-sa 4.0 with attribution required. rev 2019.11.15.35459
Такая вот ситуация.
Имеем репозиторий на сервере /var/www/git/repository/testdeploy.git
Имеем следующий хук (post-update)
Имеем каталог /var/www/testdeploy где лежит скажем так развернутый проект (по факту просто рабочая копия репозитория)
Права у /var/www/testdeploy, /var/www/testdeploy/.git/
Пользователь git добавлен в группу httpd
Пробую с локальной машины сделать git push origin master
Как так то? Почему git запцущеный из под пользоваеля git не видит что он находится внутри группы httpd
Права у данного файла:
Причем интересная особенность, если я этот хук выполню из консоли на удаленной машине из под пользователя «git», то процесс пройдет нормально.
Под другим юзером делаю со своего компа по удаленке. В том то и проблема я проверял, до хука доходит.
Проверял путем элементарного прописывания echo «Что-нибудь» в файле хука (post-update)
git обновляет ветку в репозитории /var/www/git/repository/testdeploy.git после чего выолняет хук и вываливается на комманде
git pull origin master
Если просписать владельцем git для каталога /var/www/testdeploy то все Ок. Складывается ощущение что при выполнении хука
git не понимает что он находится в группе httpd.