Why do github guys have many repositories and no projects? Meanwhile, some of their repos are actually projects | Sololearn: Learn to code for FREE!
New course! Every coder should learn Generative AI!
Try a free lesson
+ 1

Why do github guys have many repositories and no projects? Meanwhile, some of their repos are actually projects

22nd Apr 2020, 9:49 PM
Udoh Idorenyin
Udoh Idorenyin - avatar
5 Answers
+ 8
Udoh Idorenyin Are you referring to the Github feature called "Project" as described in the following link: https://github.com/features/project-management/ If so, the use of Project is optional for managing the backlog of feature stories / issues for developers. The name for this feature, "Project," has caused confusion with the general reference to a "project" that is often associated with the effort reflected in a source code repository. Ultimately, the repo is what most developers will leverage when working with Github and Github Project will be optional. In my case, I've never used Github Project since my teams use Jira or Pivotal Tracker for the same purposes. I hope this clears this up.
23rd Apr 2020, 5:46 AM
David Carroll
David Carroll - avatar
+ 7
Martin Taylor I'd say that "to permit multiple developers to work on the same code at the same time," is one of many features of git, not necessarily "the whole point of git." Rather, the primary purpose of git is to serve as a source code repository - for a single developer or a full dev team. Even with a single dev maintaining a repo, there is tremendous value in using a distributed revision control system like Github. 1. The project might gain interest and therefore increase in pull requests via new contributors and/or forks. 2. Single and/or multiple dev(s) should follow a workflow involving pull requests for new features rather than working directly off the master branch. 3. Local commits give individual developers the opportunity to experiment with an approach before pushing to the remote branch. 4. Pushing to specific remote branches could trigger an automated build, test, and deployment process benefiting any number of devs involved. I could list more, but hopefully you get the point. 😉
23rd Apr 2020, 6:14 AM
David Carroll
David Carroll - avatar
+ 6
Exactly David Carroll as in reply to Martin Taylor 's comment concerning the necessity of git to developer!! As I'm currently using git as a single developer, but I'm experiencing a lot of benefits with it one being following up my project progress and following up and tracking the changes I make on the project! Also having different versions of the same project (with a detailed description on each version) on remote controls other than having them in my local storage only.
23rd Apr 2020, 6:32 AM
Nyandago
Nyandago - avatar
+ 3
Udoh Idorenyin some people open a repo or repos with the intent of a project or projects and leave it. While others don't know how to use the repos properly. A step by step guide is often needed https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners
22nd Apr 2020, 10:09 PM
BroFar
BroFar - avatar
0
David Carroll you the man! Thanks.
23rd Apr 2020, 7:40 AM
Udoh Idorenyin
Udoh Idorenyin - avatar