Mail Archives: geda-user/2016/01/16/14:33:49
On 16/01/16 19:12, DJ Delorie wrote:
>> http://blog.scottlowe.org/2015/01/27/using-fork-branch-git-workflow/ .
> We used that flow before. Pull requests got lost, a lot of the work
> done in forks got forgotten, etc. We use the same basic flow now
> (branch-n-merge instead of fork-n-pull) but having all the "things to
> be reviewed" in one spot makes it easier to keep track of it all.
But from where I'm sitting/standing .. where IS that one spot? I see
several .. sprinkled all over your git and user's "invisible" home repos
(now I'm sure if I got a user account, I could clone these just as
easily as the next dude, but that's not my point). For anyone to be able
to review other's code .. it needs to be easily accessible, nay ..
blatantly obvious, even. I'm not sure (correct me if I'm wrong, of
course) that that is the case currently...
> There's nothing stopping you from using the fork model still, as some
> of us do. Just keep in mind that it's your responsibility to keep
> your work from being forgotten.
Of course. That's reasonably academic, but also illustrates the point
above about code being freely accessible to others.
I'll take the opportunity to clarify here .. I know people are
particular about their code and features, coding standards and what-not.
The idea is not to create a platform for people to rail against one
another, its to see what other people are working on, how they achieve
their goals, and generally open up the coding effort that's currently
going on. Perhaps with a little bit of friendly 'review' we can all
suggest improvements, and collectively improve? Also, its transparent
how to merge A's work with B and C and so forth .. at least in my eyes ..
>> I'm pretty sure this workflow is not unique to Github, it's just become
>> popular because of it.
> The details are, though:
>
> "Forking a repository is really straightforward:
> 1. Make sure you’re logged into GitHub with your account."
>
> "GitHub makes this part incredibly easy. Once you push a new branch up
> to your repository, GitHub will prompt you to create a pull request"
Yes, this is what I mean about not being unique to GitHub, but partially
becoming popular because of it. As I say, I'm still a relative newbie to
both git and github, but I can really see the power of it, and its
interface, although no reason why the command-line git tools don't
complement it either. As it's free to use, and I have nothing to hide,
this would obviously be my platform of choice (either GH or bitbucket
I've used) for my code development (and already is in a couple of cases).
MJE
- Raw text -