Yahoo Search Búsqueda en la Web

Entrar

Resultado de búsqueda

  1. stackoverflow.com › questions › 24568936What is difference between 'git reset --hard HEAD~1' and 'git...

    Learn the difference between git reset --soft and git reset --hard options, and how they affect your working tree, index and history. See examples, diagrams and explanations from experts and users.

  2. git-scm.com › docs › git-resetGit - git-reset Documentation

    Learn how to use git reset with the --soft option to reset the current HEAD to the specified state without touching the index or the working tree. See examples, options and differences with other modes of git reset.

  3. stackoverflow.com › questions › 5203535Practical uses of git reset --soft? - Stack Overflow

    Merge in the changes from the stash branch, git merge <branchname>_stash. Soft reset your existing branch to 1 before your merge, git reset --soft HEAD^. Remove your stash branch, git branch -d <branchname>_stash. Also remove your stash branch from origin, git push origin :<branchname>_stash.

  4. www.atlassian.com › es › gitgit reset | Atlassian Git Tutorial

    El comando git reset es una herramienta compleja y versátil para deshacer cambios. Se invoca principalmente de tres formas distintas, que se corresponden con los argumentos de líneas de comandos --soft, --mixed y --hard.

  5. builtin.com › software-engineering-perspectives › git-reset-soft-headHow to Undo the Last Commit Using Git Reset Command

    12 de jul. de 2022 · Learn how to use git reset --soft, --mixed, and --hard flags to change the current branch, index, and working directory. See examples, diagrams, and tips for undoing and redoing commits.

  6. www.atlassian.com › git › tutorialsGit Reset | Atlassian Git Tutorial

    Learn how to use git reset command to undo changes in Git's three trees: Working Directory, Staging Index, and Commit History. See examples of git reset with different arguments: --soft, --mixed, --hard.

  7. git-scm.com › book › enGit - Reset Demystified

    HEAD is the pointer to the current branch reference, which is in turn a pointer to the last commit made on that branch. That means HEAD will be the parent of the next commit that is created. It’s generally simplest to think of HEAD as the snapshot of your last commit on that branch. In fact, it’s pretty easy to see what that snapshot looks like.