4 ms·
Both seems non perfect to me. Having to set up one's git config or having to fork a repo seem to be accidental complexity is both cases.
by Leherenn 6y ago
Both seems non perfect to me.
Having to set up one's git config or having to fork a repo seem to be accidental complexity is both cases.
- u801e 6y agoTo be fair, setting up one's git config is a one time step. But there is a bit of effort required to keep one's GitHub fork up to date relative to the repository it was forked from.
- compsciphd 6y agogit fetch upstream ; git rebase -i upstream/master isn't that hard.
- u801e 6y agoIt depends on whether the histories have diverged and how many conflicts there are. A lot of people aren't very proficient with the use of git and will have problems (e.g., running git pull) and creating a merge commit in their branch or having conflicts they need to resolve. The next time they open a PR using that branch, it will have commits that will clutter the branch.