Содержание
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.
With version control, it is best to ignore any files and folders that are generated somehow, such as this "Microsoft" folder. With git, you can do that in your .gitignore file with the following line, assuming that "Desktop/MY REPOS/The-Tech-Academy-C-Sharp-Coding-Projects/" is your project root:
In fact, if "AppData" contains only generated files, then you can even ignore just that.
I was using Sublime Text ver 3.2.1 working on a fresh copy of laravel in wamp. I had this issue of ‘cannot publish unborn head’ when using GitHub Desktop to publish for the first time. Solved by typing something in the title under Summary. As an aside, I included .editorconfig in my gitignore file.
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», то процесс пройдет нормально.
- Вопрос задан более трёх лет назад
- 4495 просмотров
Под другим юзером делаю со своего компа по удаленке. В том то и проблема я проверял, до хука доходит.
Проверял путем элементарного прописывания echo «Что-нибудь» в файле хука (post-update)
git обновляет ветку в репозитории /var/www/git/repository/testdeploy.git после чего выолняет хук и вываливается на комманде
git pull origin master
Если просписать владельцем git для каталога /var/www/testdeploy то все Ок. Складывается ощущение что при выполнении хука
git не понимает что он находится в группе httpd.