5 ms·
I wish he would add one more since he mentioned github - don't fork unless you actually need to. I see way too many forks of projects on github with no signific
by ianstallings 13y ago
I wish he would add one more since he mentioned github - don't fork unless you actually need to. I see way too many forks of projects on github with no significant changes. If you have a bug fix make it on the same repo and then submit a pull request with your changes. Forks are for adding new features, making major changes, or if the original author is no longer maintaining the project.
- jedbrown 13y agoHow do you "make it on the same repo and then submit a pull request" without either (a) having write access to that repo or (b) forking? This is one way in which 'git send-email' is lighter weight and more convenient, provided all involved know how to use it.
- ianstallings 13y agoJesus you're right I always use the community model where one can be added to the project and submit the changes that way. I wish there was an easier way to use the proper branching model because that's what it truly is, a branch. That's not even really my beef, it's users that fork and never intend on making any changes because they don't understand how to clone. So when you search the name of the project you get a ton of results.