Read the statement by Michael Teeuw here.
GitHub/Fork/Local Git/Getting Giddified ...
-
Bwahahaha. Yeah, I think I’m going to have to ask the git community or on stackoverflow.
-
So the short answer is to squash my commits prior to syncing to GitHub. Easy enough … I have to remember to do it and only sync once per session, so like at the end of my work day, or at the end of the evening at home. That should then create a cleaner PR. This is to be tested next … after I get rid of the current fork that I have that has dozens of commits on a PR (because I synced dozens of times.) Get rid of it, refork, add my stuff back in, and then get a clean(er) PR done. Oy … headache.
-
-
Mainly GitHub for Windows (which is a GUI). And it’s really only for committing my changes, and syncing them back up to GitHub (online, into my fork). The only time I drop to command line is when I need to merge the upstream repo (so I stay current with stuff that you merge in.)
But the problem is that I have a tendency to push stuff up to GitHub (online) several times during the day, as opposed to just once at the end of the day. This then creates multiple commits in the PR. If I squash all of my commits into one, just prior to syncing, then the PR will only have 1 or 2 items in it, as opposed to one for every single commit I made throughout the day.
It’s a matter of changing how I interact with GitHub, which I suspect would be the same no matter what application I’m using.
-
@KirAsh4 Thats true indeed. I just admit. I work the same way as you: push every change! ;)
