Someone (even wiser) said to me : If git is your only problem when working on open source, then you're doing great.
More seriously though, it is important to know git, especially if you have committer privileges. And no matter how conversant you are with git, it always helps to read this page [1]. In addition to having a list of commands for common git activities, we could make things easier for newbies by providing scripts, but things like rebase, resolving merge conflicts, etc. are sort of hard to script. [1] https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell On Sun, Mar 3, 2019 at 6:33 PM Paul Rogers <[email protected]> wrote: > Hi Charles, > > As someone who struggled though learning these topics over the last few > years, I'd point out that there is no right way to do this stuff. You can > use the Git command line tools, You can use a UI. You can keep branches > locally, or publish everything to GitHub. As Parth wisely noted back when I > started with Drill, Git will be confusing until you "get" what's going on, > then it seems pretty simple. > > While Drill should probably not try to provide a full Git tutorial, I > notice that many projects do provide a set of instructions for common > tasks. These don't explain the why and how, they just act as a reference, > which is pretty handy. Anyone know of a good writeup for another project we > can reference? > > Maybe we can draft something (ideally on a Wiki, but since we don't have > one, in the developer documentation) that follows the material of other > projects, but with a Drill-specific spin. > > Thanks, > - Paul > > > > On Saturday, March 2, 2019, 5:00:13 PM PST, Charles Givre < > [email protected]> wrote: > > All, > Speaking as a non-developer, I wonder if it might be helpful to put > instructions on the CONTRIBUTING.md file that explain how to: > 1. Rebase a branch > 2. Squash commits > > I know for developers these things seem trivial, but for non-developers or > people who don’t work with git on a regular basis, it can be quite > confusing. In the last few weeks, we’ve seen a few non developers submit > PRs and they seem to be stuck on these steps. > > Thanks, > — C
