Re: creating github pull requests in pkg-perl-tools
- To: debian-perl@lists.debian.org
- Subject: Re: creating github pull requests in pkg-perl-tools
- From: Jakub Wilk <jwilk@debian.org>
- Date: Thu, 21 Jul 2016 00:33:22 +0200
- Message-id: <[🔎] 20160720223321.azk7iinira6mgpnx@jwilk.net>
- Mail-followup-to: debian-perl@lists.debian.org
- In-reply-to: <20160602215839.GA5117@xps>
- References: <20160528175535.GA12145@ktnx.net> <20160528163455.GA24318@xps> <20160528220332.GM7980@jadzia.comodo.priv.at> <CAMDxSEg_fKP=uY==Xz1Jp2+_vWeOTVvzZ9BjF=hvDrd2vgRbhA@mail.gmail.com> <20160601092412.GA24335@pcbassegoda-i-mestres.ac.upc.edu> <20160602114529.GC12145@ktnx.net> <20160602215839.GA5117@xps>
* Alex Muntada <alexm@alexm.org>, 2016-06-02, 23:58:
I am not sure how sound this is as I am not using github much, but
perhaps using an "upstream/" prefix could solve the name space
problem?
Unfortunately, you can't choose the name of the repos you fork or
mirror on GitHub. It's always /{user}/{repo} where {repo} is the same
for any forks
While GitHub doesn't let you choose the name at clone time, you can
rename the repo afterwards.
For example, I could have a fork of /alexm/foobar named
/jwilk/upstream-foobar (but not /jwilk/upstream/foobar).
Or one could create new organization, say "debupstream"[0] and put the
fork at /debupstream/foobar/.
[0] Sadly, the organization "upstream" is already taken.
--
Jakub Wilk
Reply to: