Good point.
I contracted the title from "A script containing Git commands that create a
repo and uploads to GitHub".


On Tue, Sep 27, 2016 at 8:17 AM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:

> On Tue, 27 Sep 2016 06:56:06 -0700 (PDT)
> Wilson Mar <wilson...@gmail.com> wrote:
>
> > I'd like your opinion of a shell script I created at:
> > https://github.com/wilsonmar/git-utilities/blob/master/git-
> sample-repo-create.sh
> >
> > I created it as part of my Master class on Git and GitHub
> > to provide a way for people to see an entire sequence of Git commands.
> > People can change something and see the impact on the chain of events
> > and log outputs.
> >
> > The script is idempotent - it creates a new repo locally each run,
> > but first deletes folders created from the previous run.
> >
> > Same thing with creating a repo.
> > The script obtains a token from GitHub by providing a user's password,
> > then uses the token to create a repo.
> > On the next run it deletes the repo before starting again.
> >
> > The script pulls in a .secrets file containing the GITHUB_PASSWORD
> > for the account and GITHUB_TOKEN.
>
> I have no idea what this script really does, but I'd like to warn you
> that you possibly may be confusing Git with Github in your head -- I'm
> judging from the name of the script and the repository it's located in.
>
> You should get this distinction very well understood: Git is a
> standalone software package which makes no use of Github.  Github is a
> hosting provider for Git repositories, which adds a web interface to
> manipulate the server-side replicas of your repositores, manage access
> to them etc, and exposes a web API to do some of these manipulations in
> an automatable way.
>
> Hence Github makes use of Git, but the reverse is not true.
> That is, to start working with Git on an existing project, you just go
> on and call `git init .` in the project's directory.  That's all.
> You do not even need a remote repository hosted somewhere: Git
> repositories are completely free-standing.  And if you need one, it's
> not necessarily should be hosted by Github: it may be another directory
> on your filesystem (or on a filesystem on your pendrive), it may reside
> on a nearby computer, or on a corporate server.  Or you can use another
> public Git hosting provider such as Bitbucket.
>
> If you do understand all this stuff, please excuse me for reiterating
> it.  But in any case please do not confuse your users.  This confusion
> between Git and Github is a real thing, and it's bad because it
> actually takes away from the knowledge of your users.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to