From: <rsbecker@nexbridge.com>
To: "'Sean Allred'" <allred.sean@gmail.com>, <lbdyck@gmail.com>
Cc: <git@vger.kernel.org>
Subject: RE: git client enhancement request
Date: Mon, 13 May 2024 15:09:07 -0400 [thread overview]
Message-ID: <019201daa569$0ae28f20$20a7ad60$@nexbridge.com> (raw)
In-Reply-To: <m0pltptx3h.fsf@epic96565.epic.com>
On Monday, May 13, 2024 1:56 PM, Sean Allred wrote:
><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.
Please have a look at the github/bitbucket/gitlab/azuregit REST API for doing what you are trying to do. There is no specific "git client" function as git is symmetrical.
--Randall
next prev parent reply other threads:[~2024-05-13 19:09 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
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 [this message]
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='019201daa569$0ae28f20$20a7ad60$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=allred.sean@gmail.com \
--cc=git@vger.kernel.org \
--cc=lbdyck@gmail.com \
/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).