We have already been at this point three weeks ago.
so I’ll have a look at GitHub in the next days and try to get familiar with it.
For your own progress (in doing this and learning to use GitHub), please stop taking these “maximum effort approaches” of “try[ing] to get familiar with it”: You will read some documentation and become fearful of the complexity, again.
Please simply perform these steps:
- Create a GitHub account, preferably with a name which lets people recognise you, e.g.
Seven.of.nine. - Go to
direc85’sharbour-gpsinfosource code repository while being logged in at GitHub. - Hit the
forkbutton there, then GitHub will create and display your clone of this repository. - Employ your changes in your clone of
harbour-gpsinfowith GitHub’s web-editor (by copy&pasting) and GitHub will suggest to pose a pull-request to the original repository (i.e.direc85’s):
Do as suggested and you are finished by reaching your goal!
Just do that, i.e. cease revolving around “trying to get familiar”, using workarounds (as here) etc.: You simply waste your and many other people’s time.
If anything does not work for you, do ask.
Also I wrote a PM to @direc85 and will see what he’ll say to it.
The GitHub process eliminates all this manual churn of writing separate personal messages, asking people for feedback in this forum etc.! It does all that implicitly in a single place: GitHub’s web-frontend.
P.S.: An do not listen to people who suggest using git at the command line or the SailfishOS-OBS, SailfishOS:Chum, whatever else: All this is more complex than starting to use GitHub’s web-frontend.
Actually this task is optimal for performing the first steps at GitHub while doing something practical (and not just as a learning lesson).