Ya estoy inscrito ¿Todavía no tienes acceso? Nuestros Planes
Ya estoy inscrito ¿Todavía no tienes acceso? Nuestros Planes
Solucionado (ver solución)
Solucionado
(ver solución)
2
respuestas

Mensaje largo al ejecutar "git ad ." en el ejercicio de Branches

Haciendo el ejercicio de Branches, al ejecutar el comando "GIT ADD ." me arrojó el mensaje que copio:

m@DESKTOP-JVTBCB4 MINGW64 ~/Documents/ONE/GIT (main) $ git checkout titulo Switched to branch 'titulo'

m@DESKTOP-JVTBCB4 MINGW64 ~/Documents/ONE/GIT (titulo) $ git status On branch titulo Untracked files: (use "git add ..." to include in what will be committed) Ana/ servidor/

nothing added to commit but untracked files present (use "git add" to track)

m@DESKTOP-JVTBCB4 MINGW64 ~/Documents/ONE/GIT (titulo) $ git add . warning: adding embedded git repository: Ana/proyecto hint: You've added another git repository inside your current repository. hint: Clones of the outer repository will not contain the contents of hint: the embedded repository and will not know how to obtain it. hint: If you meant to add a submodule, use: hint: hint: git submodule add Ana/proyecto hint: hint: If you added this path by mistake, you can remove it from the hint: index with: hint: hint: git rm --cached Ana/proyecto hint: hint: See "git help submodule" for more information. warning: in the working copy of 'servidor/HEAD', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/config', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/description', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/applypatch-msg.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/commit-msg.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/fsmonitor-watchman.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/post-update.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/pre-applypatch.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/pre-commit.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/pre-merge-commit.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/pre-push.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/pre-rebase.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/pre-receive.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/prepare-commit-msg.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/push-to-checkout.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/hooks/update.sample', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/info/exclude', LF will be replaced by CRLF the next time Git touches it warning: in the working copy of 'servidor/refs/heads/master', LF will be replaced by CRLF the next time Git touches it

A que se debe? Habrá algún paso previo que no realice?

2 respuestas
solución!

Lo que te indican esos mensajes es que se a creado un submodulo cosa que no debió de pasar estuve leyendo y no logro encontrar la causa. Lo que si e visto es que la solución que mas usan es borrar la carpeta oculta .git la cual está dentro dentro tu carpeta raíz del proyecto(la carpeta donde está tu archivo index.html). El problema es que al borrar esa carpeta se pierde los cambios hechos me parece así que tendrías que repetir todo lo del curso.

Gracias! Luego comprendí cual fue el error que cometí y causo ese mensaje, y si tuve que hacer todo desde cero nuevamente.