Hello,
If the changes are minor, you can avoid the issue of branches / pushing by
simply sending us commits as patches. (You mentioned that you wanted to
make a trivial adjustment to a PAMELA script.)
If you wanted to do that, you would commit your changes and then run:
git format-patch -1
(Where the -1 option specifies the number of commits to export.) Such
patch files contain the commit message etc. and can be turned back into
Git commits with the "git am" command -- I would be happy to do so and
push the commits to the repository.
Best regards,
Graham
On Mon, 7 Jan 2019, Tim Jenness wrote:
> I think the problem is that we have configured the submodules to be
> relative rather than absolute URLs (GitHub really really wants you to use
> absolute URLs) so when you fork the build fails because it can't found the
> submodules. You can overcome that by using the main repo for the build and
> then changing the remote URL to your fork when you push.
>
> On Mon, Jan 7, 2019 at 10:46 AM Tom Marsh <[log in to unmask]> wrote:
>
>> Something I didn't understand with forking was that I tried doing an
>> installation from a fork of the repository and everything fell over badly,
>> so clearly one was install from a clone of the main repository. But having
>> made changes, in the fork case, is it a matter of re-directing 'git push'
>> to update the fork rather than the main repository?
>>
>> tom
>>
>> ########################################################################
>>
>> To unsubscribe from the STARDEV list, click the following link:
>> https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=STARDEV&A=1
>>
>
> ########################################################################
>
> To unsubscribe from the STARDEV list, click the following link:
> https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=STARDEV&A=1
>
########################################################################
To unsubscribe from the STARDEV list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=STARDEV&A=1
|