To fork an existing cookbook repository on GitHub.
Table of Contents
Access to the cookbook repository that you want to fork. You can fork any public repository, but if you want to fork a private repository, you must contact the repository owner to request access.
Note: In order to submit code submissions, you must complete a RightScale Contributors Agreement found here.
If you want to contribute code enhancements to an existing repository, you should create a new repository by creating a fork of the original. For example, if you want to contribute minor bug fixes, enhancements, or new features to another git project, the easiest way for those changes to be merged into the original repository is with a Pull Request from a forked repository. See Make a Pull Request on GitHub.
Note: When you fork a repository, all metadata associated with the repository such as commit messages, branches, tags, etc. are copied over to the new repository so that it's an exhaustive duplicate of the repository and all of its contents.
The easiest way to fork a cookbook repository from GitHub's web interface or use the command line utility, Knife, on your Chef development machine.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.