Definitely helps, thanks. I wasn’t sure how mirror repos work, and was
allowing for the possibility they might be substantially different from
ordinary repos. This makes things easier.
On 4/29/17, 6:35 PM, "Greg Stein" <gst...@gmail.com> wrote:
On Sat, Apr 29, 2017 at 12:24:53AM -0700, Matt Foley wrote:
>...
> ‘B’ may or may not be important, depending on how
> Apache INFRA goes about changing the name of the Github apache/metron
> mirror repo. If they use the standard Github owner’s command
> for renaming a repo, then Github maintains semantics for users of the
> prior name. Then, you wouldn’t have to do anything about the
> name change unless you wanted to.
Yes, we just rename it via the web UI. I'm not sure what other
alternatives are even remotely viable :-P
>...
> ‘D’ finally is perhaps the most difficult question. Every fork repo in
Github “knows” what repo it was forked from, and uses that as the default for
Pull Requests generated from the fork. Can this be changed?
>
> If Apache INFRA respects the Github protocol for repo renaming, then
> we don’t need to change anything. We can just rely on the
> semantic preservation in the protocol and new PRs generated will
> automatically point at the renamed Apache repository, directly or
> indirectly. That would be best, because Github does NOT provide any
> easy means for changing the “fork upstream” pointer.
Yup. Just a rename. We don't want to lose a project's associated
GitHub data (issues, PRs, etc)
>...
Hope that helps,
Greg Stein
Infrastructure Administrator, ASF
