Search results for work tree

Distributed Workflows
/book/en/Distributed-Git-Distributed-Workflows
to utilize some of the distributed workflows that Git affords you.In this chapter, you’ll see how to work with Git in a distributed environment as a contributor and an integrator. That is
Branching Workflows
/book/en/Git-Branching-Branching-Workflows
— possibly only code that has been or will be released. They have another parallel branch named develop or next that they work from or use to test stability — it isn’t
Signing Your Work
/book/en/Git-Tools-Signing-Your-Work
Signing Your Work Git is cryptographically secure, but it’s not foolproof. If you’re taking work from others on the internet and want to verify that
Working with Remotes
/book/en/Git-Basics-Working-with-Remotes
others involves managing these remote repositories and pushing and pulling data to and from them when you need to share work. Managing remote repositories includes knowing how to add remote
git-read-tree
/docs/git-read-tree
, or a 3-way merge, with the `-m` flag. When used with `-m`, the `-u` flag causes it to also update the files in the work tree with the result of the merge. Only trivial merges are done by 'git read
git-commit-tree
/docs/git-commit-tree
git-commit-tree(1) ================== NAME ---- git-commit-tree - Create a new commit object SYNOPSIS -------- [verse] 'git commit-tree' <tree> [(-p )...] 'git commit-tree' [(-p
git-merge-tree
/docs/git-merge-tree
git-merge-tree(1) ================= NAME ---- git-merge-tree - Perform merge without touching index or working tree SYNOPSIS -------- [verse] 'git merge-tree' [--write-tree] []
git-diff-tree
/docs/git-diff-tree
submodules are not considered dirty when they only contain untracked content (but they are still scanned for modified content). Using "dirty" ignores all changes to the work tree of submodules, only
git-worktree
/docs/git-worktree
trees attached to the same repository. A git repository can support multiple working trees, allowing you to check out more than one branch at a time. With `git worktree add` a new working tree is
Contributing to a Project
/book/en/Distributed-Git-Contributing-to-a-Project
that. Because Git is very flexible, people can and do work together in many ways, and it’s problematic to describe how you should contribute — every project is a bit different. Some of the variables
Administration
/book/en/Appendix-C:-Git-Commands-Administration
> command goes through a log of where all the heads of your branches have been as you work to find commits you may have lost through rewriting histories. We cover this
Replace
/book/en/Git-Tools-Replace
, which is 9c68fdc in SHA-speak. So, our base commit will be based off of that tree. We can create our base commit using the commit-tree command, which just takes a tree and will
Branches in a Nutshell
/book/en/Git-Branching-Branches-in-a-Nutshell
Nearly every VCS has some form of branching support. Branching means you diverge from the main line of development and continue to do work without messing with that main line. In many VCS tools
What is Git?
/book/en/Getting-Started-What-is-Git?
VPN. If you get on an airplane or a train and want to do a little work, you can commit happily (to your local copy, remember?) until you get to a network connection to upload. If you go home
Git as a Client
/book/en/Git-and-Other-Systems-Git-as-a-Client
successfully integrated into the working tree. Please see the above messages for details. Now, all your work is on top of what is on the Subversion
git-write-tree
/docs/git-write-tree
git-write-tree(1) ================= NAME ---- git-write-tree - Create a tree object from the current index SYNOPSIS -------- [verse] 'git write-tree' [--missing-ok] [--prefix=
git-ls-tree
/docs/git-ls-tree
git-ls-tree(1) ============== NAME ---- git-ls-tree - List the contents of a tree object SYNOPSIS -------- [verse] 'git ls-tree' [-d] [-r] [-t] [-l] [-z] [--name-only] [--name-status
gitcli
/docs/gitcli
. `git diff -- HEAD` is, "I have a file called HEAD in my work tree. Please show changes between the version I staged in the index and what I have in the work tree for that file", not "show the
gitcore-tutorial
/docs/gitcore-tutorial
'working directory'), but to actually check in your hard work, you will have to go through two steps: - fill in the 'index' file (aka 'cache') with the information about your working tree state
git-rm
/docs/git-rm
version 1.7.8 or newer) will be removed from the work tree, as their repository lives inside the .git directory of the superproject. If a submodule (or one of those nested inside it) still uses a .git