Git

Search results for fork

  1. Contributing to a Project

    /book/en/GitHub-Contributing-to-a-Project

    don’t have push access, you can “fork” the project. When you “fork” a project, GitHub will make a copy of the project that is entirely yours; it lives in your namespace, and you can push to it.

  2. Maintaining a Project

    /book/en/GitHub-Maintaining-a-Project

    in a fork of your repository or they can come from another branch in the same repository. The only difference is that the ones in a fork are often from people where you can’t push to their branch and

  3. GitLab

    /book/en/Git-on-the-Server-GitLab

    merge request from their branch back into master or any other branch. Users who don’t have push permissions for a repository can “fork” it to create their own copy, push commits to

  4. Distributed Workflows

    /book/en/Distributed-Git-Distributed-Workflows

    ">Figure 54. Integration-manager workflow This is a very common workflow with hub-based tools like GitHub or GitLab, where it’s easy to fork a project and push

  5. Managing an organization

    /book/en/GitHub-Managing-an-organization

    personal accounts, organizations are free if everything you plan to store there will be open source. As an owner in an organization, when you fork a repository

  6. Account Setup and Configuration

    /book/en/GitHub-Account-Setup-and-Configuration

    sign up - the account we just created comes into play when we fork projects and push to our forks a bit later. If you’d like to use SSH remotes, you’ll need to

  7. Contributing to a Project

    /book/en/Distributed-Git-Contributing-to-a-Project

    you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository

  8. git-merge-base

    /docs/git-merge-base

    merge-base' [-a|--all] --octopus ... 'git merge-base' --is-ancestor 'git merge-base' --independent ... 'git merge-base' --fork-point [] DESCRIPTION

  9. SubmittingPatches

    /docs/SubmittingPatches

    /git/git/builds/120473209 Follow these steps for the initial setup: . Fork https://github.com/git/git to your GitHub account. You can find detailed instructions how to fork here: https

  10. commit-graph

    /docs/commit-graph

    split across multiple forks in a fork network. The typical case is a large "base" repo with many smaller forks. As the base repo advances, it will likely update and merge its commit-graph chain more

  11. git-rebase

    /docs/git-rebase

    current branch. If is not specified, the upstream configured in branch..remote and branch..merge options will be used (see linkgit:git-config[1] for details) and the `--fork

  12. MyFirstContribution

    /docs/MyFirstContribution

    integration suite for you. It's documented at http://gitgitgadget.github.io. [[create-fork]] === Forking `git/git` on GitHub Before you can send your patch off to be reviewed using GitGitGadget

  13. gitworkflows

    /docs/gitworkflows

    : "] ===================================== Make a side branch for every topic (feature, bugfix, ...). Fork it off at the oldest integration branch that you will eventually want to merge it into

  14. git-pack-objects

    /docs/git-pack-objects

    naive repack may find that the optimal delta for an object is against a base that is only found in another fork. But when a client fetches, they will not have the base object, and we'll have to find a

  15. api-trace2

    /docs/api-trace2

    -id.) + Note that the `t_rel` field contains the observed run time in seconds for the child process (starting before the fork/exec/spawn and stopping after the waitpid() and includes OS process creation

  16. gitweb.conf

    /docs/gitweb.conf

    column with date of the most current commit on the projects list page. It can save a bit of I/O and a fork per repository. $omit_owner:: If true prevents displaying information about repository owner

  17. git-config

    /docs/git-config

    mode (or when an `--exec` option was provided). This is the same as specifying the `--reschedule-failed-exec` option. rebase.forkPoint:: If set to false set `--no-fork-point` option by default