Search results for work space

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-worktree
/docs/git-worktree
new branch whose name is the final component of ``, which is convenient if you plan to work on a new topic. For instance, `git worktree add ../hotfix` creates new branch `hotfix` and checks it out
Git Configuration
/book/en/Customizing-Git-Git-Configuration
how you can make Git operate in a more customized fashion, by introducing several important configuration settings and the hooks system. With these tools, it’s easy to get Git to work exactly the way
Sharing and Updating Projects
/book/en/Appendix-C:-Git-Commands-Sharing-and-Updating-Projects
operate on the local database. When you are ready to share your work or pull changes from elsewhere, there are a handful of commands that deal with remote repositories.
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
Advanced Merging
/book/en/Git-Tools-Advanced-Merging
all, if at all possible, try to make sure your working directory is clean before doing a merge that may have conflicts. If you have work in progress, either commit it to a temporary branch or stash it
Maintenance and Data Recovery
/book/en/Git-Internals-Maintenance-and-Data-Recovery
imported repository, or recover lost work. This section will cover some of these scenarios. Maintenance Occasionally, Git
Branching and Merging
/book/en/Appendix-C:-Git-Commands-Branching-and-Merging
work but pretends like it’s just a new commit without recording the history of the branch you’re merging in) at the very end of Forked Public Project.
gitcore-tutorial
/docs/gitcore-tutorial
" Git commands to set up and work with a Git repository. If you just need to use Git as a revision control system you may prefer to start with "A Tutorial Introduction to Git" (linkgit:gittutorial[7
git-commit-tree
/docs/git-commit-tree
; if specified, it must be stuck to the option without a space. `--no-gpg-sign` is useful to countermand a `--gpg-sign` option given earlier on the command line. Commit Information
git-status
/docs/git-status
files. Because it takes extra work to find untracked files in the filesystem, this mode may take some time in a large working tree. Consider enabling untracked cache and split index if supported (see
SubmittingPatches
/docs/SubmittingPatches
which covers many of these same guidelines. [[choose-starting-point]] === Choose a starting point. As a preliminary step, you must first choose a starting point for your work. Typically this means
partial-clone
/docs/partial-clone
. The goal of this work is to allow Git to better handle extremely large repositories. During clone and fetch operations, Git downloads the complete contents and history of the repository. This
multi-pack-index
/docs/multi-pack-index
space or excessive repack times. The multi-pack-index (MIDX for short) stores a list of objects and their offsets into multiple packfiles. It contains: * A list of packfile names. * A sorted list of
diff-format
/docs/diff-format
deletion or unmerged. . a space. . sha1 for "src"; 0\{40\} if creation or unmerged. . a space. . sha1 for "dst"; 0\{40\} if deletion, unmerged or "work tree out of sync with the index". . a space
git-cvsserver
/docs/git-cvsserver
commit` to work. See linkgit:gitcvs-migration[7]. [[configaccessmethod]] All configuration variables can also be overridden for a specific method of access. Valid method names are "ext" (for SSH access
git-count-objects
/docs/git-count-objects
-readable] DESCRIPTION ----------- Counts the number of unpacked object files and disk space consumed by them, to help you decide when it is a good time to repack. OPTIONS ------- -v:: --verbose