From: bruce <badouglas@gmail.com>
To: git@vger.kernel.org
Subject: not sure if this is appropriate -- GH/Github question
Date: Sat, 6 Jun 2020 16:36:32 -0400 [thread overview]
Message-ID: <CAP16ngr=cTTUzSb8=beKu5wtaDCXL2tECUSUg8t+1HS12O972A@mail.gmail.com> (raw)
Testing the "create fork" process using the "GH" Github cli.
The test process is:
Trying to have a Github organization with a single test user "foo"
I create the Github org -- gets http://github.com/numinds
I create a test user "foo"
I have a test VM, with a test user "test"
For test, I create the ssh priv/pub key
On the test VM, I also install GH to use the cli
-I also have the following
cat /home/test/.config/gh/config.yml
hosts:
github.com:
oauth_token: 111111
user: foo
editor: vi
I'm trying to fork the
http://github.com/drupal/drupal to be in the http://github.com/numinds
I can do:
(in the /home/test/numinds dir)
gh repo create drupal
This creates the http://github.com/numinds/drupal (blank/bare repo)
as well as the /home/test/numinds/drupal cloned repo in the local dir
However, doing:
gh repo fork https://github.com/drupal/drupal numinds/drupal
Doesn't work as I'd like it to:
I'm trying to have the drupal repo be http://github.com/numinds/drupal <<<
Instead, it creates the drupal repo in/under the "foo" user >>>> doing
somethig wrong!
It generates the repo as:
https://github.com/t-smith1/drupal
Any pointers/clues on what I'm missing.
I have the latest version of GH v0.9.0
I have everything I can possibly view in the "member_privileges" page checked!
https://github.com/organizations/numinds/settings/member_privileges
Thoughts/Pointers on this.
Thanks
next reply other threads:[~2020-06-06 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 20:36 bruce [this message]
2020-06-08 12:40 ` not sure if this is appropriate -- GH/Github question Derrick Stolee
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP16ngr=cTTUzSb8=beKu5wtaDCXL2tECUSUg8t+1HS12O972A@mail.gmail.com' \
--to=badouglas@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).