git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <lbdyck@gmail.com>
To: "'Sean Allred'" <allred.sean@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: git client enhancement request
Date: Mon, 13 May 2024 13:02:36 -0500	[thread overview]
Message-ID: <04a101daa55f$bd15ce50$37416af0$@gmail.com> (raw)
In-Reply-To: <m0pltptx3h.fsf@epic96565.epic.com>

Is this technically feasible - that I don't know but it would seem to be. Since there are tools for github/gitlab/bitbucket that can do it then why not the standard git client.

I know that for GitHub I can also do it with curl (haven't checked the others).

What I'm trying to do is to have a usable wrapper around git for the novice and not require other packages.

One would think that it would be comparable to a "git push" but with the addition of the "git url" and some indication if the new repo is to be public or private. If it already exists then return an error message. And if it doesn't already exist then do whatever the current web interface to the git server does to define an empty repository. Having a requirement for an existing local repository would be reasonable for this to work.

I'm just asking if it can be done.

Thank you


Lionel B. Dyck <>< 
Github: https://github.com/lbdyck
System Z Enthusiasts Discord: https://discord.gg/sze

“Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are.”   - - - John Wooden

-----Original Message-----
From: Sean Allred <allred.sean@gmail.com> 
Sent: Monday, May 13, 2024 12:56 PM
To: lbdyck@gmail.com
Cc: git@vger.kernel.org
Subject: Re: git client enhancement request

<lbdyck@gmail.com> writes:
> I would like to see the option to allow the git client to request the 
> creation of a new empty git repository on the git server without 
> having to open the web interface to the git server to define a new 
> repository.
>
> Perhaps something like:  git server-repo public/private name

Is this even technically feasible? My understanding is that storage implementations of each forge vary *wildly*. I don't believe this would be under Git's ability to implement as a project.

You might look into combining your preferred forge's CLI with git
aliases:

  - GitHub has 'gh': https://cli.github.com
  - GitLab has 'glab' https://docs.gitlab.com/ee/editor_extensions/gitlab_cli

so you could alias

    git config alias.server-repo '!gh repo create'

to get something of what you want.

I believe GitLab also has a feature where you can create repositories just by pushing an existing repository to an empty project path.

--
Sean Allred


  reply	other threads:[~2024-05-13 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13 15:07 git client enhancement request lbdyck
2024-05-13 17:56 ` Sean Allred
2024-05-13 18:02   ` lbdyck [this message]
2024-05-13 18:51   ` Junio C Hamano
2024-05-13 19:00     ` lbdyck
2024-05-13 21:19       ` brian m. carlson
2024-05-13 19:09   ` rsbecker
2024-05-13 19:11     ` lbdyck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='04a101daa55f$bd15ce50$37416af0$@gmail.com' \
    --to=lbdyck@gmail.com \
    --cc=allred.sean@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).