On 2021-08-18 4:44 AM (-4), clipka wrote:
> Am 18.08.2021 um 00:17 schrieb Cousin Ricky:
> 
>> [...]  I do not need or want offline
>> Git capabilities;
> 
> While the GitHub web interface alone may be sufficient for an occasional
> small contribution here and there (by now; even that hadn't always been
> the case) in which only a single file is changed; but for anything
> beyond that, I'd really recommend using a proper Git UI on your machine
> (which may just be the `git` command-line interface, or a 3rd party
> GUI), which (by Git's design) invariably also means a having local
> repository.

Would I have to uproot my existing local directory tree?

>> I already have my projects organized locally in
>> folders, and to bring in an SCM would be more effort that it's worth at
>> this time.
> 
> An SCM is exactly what Git is, so I'm rather puzzled?!

I mean I don't need an SCM on my local machine.  I vaguely recall having
to use one on the job many years ago, and I seem to have spent as much
time wrestling with the SCM as I did writing code.  They confuse the
hell out of me, which would seem to defeat their own purpose.

>> I want organization on GitHub, and even if I did reorganize
>> my local POV-Ray directory tree to use Git, I see no indication that
>> this organization could be uploaded intact.
> 
> If you "upload" the stuff (or "commit" and "push", as the technical
> terms would be) using some arbitrary Git interface that supports
> submodules/subtrees, that hierarchy _will_ end up intact on the GitHub
> repo.
> 
> Whether that hierarchy is also exposed to the user is another matter;
> but I recommend that you see for yourself.

The user's view is precisely what I'm concerned about.

> Here's an example of how GitHub themselves use _submodules_ in one of
> their own projects, `linguist`, a tool they use to detect the
> programming language of files in a repository; each folder in its
> `vendor/grammars` directory is actually a submodule:
> 
> https://github.com/github/linguist/tree/master/vendor/grammars

That looks like what I'm looking for.  How do I actually do it?  Is
there a gentle introduction somewhere to how it's done, because GitHub
has only the barest tutorial on how to use its UI, and everything else I
can find, whether in GitHub's docs, GitHub's blog, or third party
instructions, just dumps me into the deep end of the pool.  I seem to
lack an overall conceptual framework of what's going on.

Post a reply to this message