![]() Software repositories are increasingly essential to support the management of typical artifacts building up projects, including source code, documentation, and bug reports. Moreover, our results show the value of recommendation and provide important insights for GitHub to recommend repositories. Our results show that forking is mainly used for making contributions of original repositories, and it is beneficial for OSS community. In comparison with unattractive repository owners, attractive repository owners have higher percentage of organizations, more followers and earlier registration in GitHub. (3) Developers mostly fork repositories from creators. (2) A repository written in a developer’s preferred programming language is more likely to be forked. Developers care about repository owners when they fork repositories. More than 42 % of developers that we have surveyed agree that an automated recommendation tool is useful to help them pick repositories to fork, while more than 44.4 % of developers do not value a recommendation tool. Developers find repositories to fork from various sources: search engines, external sites (e.g., Twitter, Reddit), social relationships, etc. ![]() Our main observations are: (1) Developers fork repositories to submit pull requests, fix bugs, add new features and keep copies etc. ![]() We make surveys, and analyze programming languages and owners of forked repositories. We collect a dataset containing 236,344 developers and 1,841,324 forks. In this paper, we explore why and how developers fork what from whom in GitHub. A deep understanding of repository forking can provide important insights for OSS community and GitHub. Developers freely fork repositories, use codes as their own and make changes. Though forking is controversial in traditional open source software (OSS) community, it is encouraged and is a built-in feature in GitHub. coding 2.Forking is the creation of a new software repository by copying another repository. & git commit –amend”, the SHA value of your commit changes but the change-id won’t change.Ĭhange-id will help gerrit to recognize all your versions of the same commit.įollow the following step to push a commit to gerrit. This commit-msg hook is a small tool that will generate a change-id whenever you create a new commit.Īfter your “git add. In the step 4 in the previous section, you need to clone with commit-msg hook. It’s like you have different versions of a single commit. & git commit –amend” to “change the history” instead of using “git add. In other words, you need to use “git add. It’s time to learn how to work with gerrit.Īfter you push your code to gerrit, reviewers will review your code and give you comments.Īfter you update your code and address all the comments, you need to change the current commit instead of creating a new commit. Now you have your ndn-cxx downloaded from gerrit. Specifically, you need to use Clone with commit-msg hook. Using ndn-cxx as an example, find ndn-cxx among the project list and click its name to go into ndn-cxx’s page () 4. ![]() ![]() Using the nav bar, go to BROWSE -> Repositories and select the project that you want to work on Select the project that you want to download If you don’t have this file, please Google “github generate SSH key” and generate a key pair for your deviceģ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |