Skip to content

Instantly share code, notes, and snippets.

@remram44

remram44/github-remove-fork.txt Secret

Last active Aug 29, 2015
Embed
What would you like to do?
---------- Email message ----------
From: Rémi Rampin <remi.rampin@nyu.edu>
Date: 2014-11-11 12:34 GMT-05:00
Subject: Opening pull requests against the right fork
To: GitHub Staff <support@github.com>
Hi Github,
We have a project, UV-CDAT/VisTrails, that is technically a fork of VisTrails/VisTrails and we have it marked as such on Github. However, we do not mean to merge things back from there to the original repository.
The problem is that everytime someone tries to open a pull requests in UV-CDAT/VisTrails, the pull requests by default has VisTrails/VisTrails as the base repository. We have to manually change that base to UV-CDAT/VisTrails, or else accidents happen (like here <https://github.com/VisTrails/VisTrails/pull/956>).
Can something be done about that? Is this a limitation of forks on Github? Do we have to lose the fork relation altogether?
Thanks
--
Rémi Rampin
VisTrails developer
Polytechnic School of Engineering of New York University
---------- Email message ----------
From: John Greet (GitHub Staff) <support@github.com>
Date: 2014-11-12 3:00 GMT-05:00
Subject: Re: Opening pull requests against the right fork
To: Rémi Rampin <remi.rampin@nyu.edu>
Hi Rémi,
This is a limitation of fork networks on GitHub. If you'd like, we could remove UV-CDAT/VisTrails from the VisTrails/VisTrails fork network making it a standalone repository.
Contributors with their own forks would have make new forks of UV-CDAT/VisTrails in order to submit pull requests to it, but UV-CDAT/VisTrails would be the new default target for PRs.
Let us know if you'd like to proceed.
Cheers,
John
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.