uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: Git struggles, basics
Date Tue, 09 Oct 2018 20:45:19 GMT
just curious, why doesn't this work:

1) clone project to local pc
2) create branch, make updates
3) commit changes
4) create a pull request for that commit

Is it because with this approach, my pull request would somehow need to
reference my clone on my local pc which others of course don't have access to?
I kind of thought the pull request would "encapuslate" all the info it needed,
sort of like a patch.

For this particular case, what I did was:
1) clone project to local pc
2) create branch, make updates
3) make a "git"-style "patch" and attach the patch to the Jira.

:-) Cheers. -Marshall

On 10/9/2018 4:26 PM, Richard Eckart de Castilho wrote:
> On 9. Oct 2018, at 19:38, Marshall Schor <msa@schor.com> wrote:
>> Still confused.
>> It appears I can do
>> git clone https://gitbox.apache.org/repos/asf/maven-gpg-plugin.git  OR
>> git clone https://github.com/apache/maven-gpg-plugin  
>> Are these the same thing?
> Yes and no :) 
> Yes: you'll end up with the same code in both cases because ASF GitBox syncs with GitHub
> No: in the first case the "remote" of your clone will be ASF gitbox and in the second
>     the "remote" of your clone will be GitHub. In both cases, you could still add the
>     one as a second "remote" to your local clone. Both probably won't get you far if
>     want to contribute code because you likely have commit permissions to neither of
the two
>     repositories.
> Because of that you'd probably first want to go to the GitHub website, fork the "maven-gpg-plugin"
> repo under your own GitHub account, then clone *that*. If you have already cloned any
of the
> others, you can could create the fork and add it as another remote to your local clone.
> Then, you create a branch, and commit your changes to that branch and push it to the
> forked repo under your GitHub account. Once the changes have been pushed there, you
> create a "pull request" via the GitHub website.
> Really, it sounds more complicated than it really is because there are so many ways
> that lead to more-or-less the same result, so I'll summarize the path of least resistance

> briefly:
> 1) fork repo on github
> 2) clone fork to your local pc
> 3) create branch
> 4) commit changes
> 5) push branch
> 6) create pull request
> Cheers,
> -- Richard

View raw message