How do github forks work




















Undoing changes git checkout git clean git revert git reset git rm. Rewriting history git commit --amend git rebase git rebase -i git reflog. Collaborating Syncing git remote git fetch git push git pull. Using branches git branch git checkout git merge Merge conflicts Merge strategies. Migrate to Git from SVN. Perforce to Git - why to make the move. Migrating from Perforce to Git. How to move a Git repository with history. Advanced Tips Advanced Git Tutorials. Merging vs.

Resetting, Checking Out, and Reverting. Git submodules. Git subtree. Large repositories in Git. Git LFS. Git gc. Basic git commands 4. Undoing things 5. Navigate GitHub repos 6. Fork a GitHub repo 7. Create pull requests. Learning objectives At the end of this activity, you will: Be able to create a fork, or copy, of a GitHub repository within your Github account.

Know how to navigate between your GitHub repository and a forked GitHub repository. Be able to explain how your forked repository relates to the original repository that it was created from.

What you need A GitHub user account A terminal running bash, and git installed and configured on your computer. Follow the setup instructions here: Setup instructions. And who knows--maybe someone you've never met will find your changes much more valuable than the original project. You've successfully forked and contributed back to a repository. Go forth, and contribute some more!

For more information, see " Finding ways to contribute to open source on GitHub. All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request. Or, learn how to contribute. GitHub Docs. Learning about GitHub. Signing up for GitHub. Using GitHub. Explore projects. Getting started with Git. Using Git.

Contributing to projects. In this article About forking. You have two options:. It hides lots of detail and can feel quite magical. Regardless, get yourself into this project, whatever that means for you, using your usual method. Explore the new repo in some suitable way. If it is a package, you could run the tests or check it.



0コメント

  • 1000 / 1000