[yt-dev] what to do with fork once PR approved?

[Nathan Goldbaum]

Hi Geoffrey,

Personally, I like keeping around a personal fork of yt so that I can issue pull requests for lightweight new features as well as bugs and the like.  

If I were working on a relatively large new feature that would take more than a few days to implement, I would create a new fork, do the work in there, merge in mainline once I was done, and issue a pull request.  Once the PR was accepted, I would delete the fork.

Whether or not you keep the fork is entirely up to you.  The existence of the fork will not affect the main yt development repository.

Nathan



On Jun 26, 2012, at 2:19 PM, Geoffrey So <gsiisg at gmail.com> wrote:

> Hi yt-devs, I was wondering what to do with my fork after the pull request was accepted.  Do you guys usually delete the fork and create a new one if something needed to be changed later, or keep the current fork and pull from the main yt-dev to keep it up to date before making changes?  Just feels redundant keeping the old fork around now, but maybe there are advantages I did not consider.
> 
> From
> G.S.
> !DSPAM:10175,4fea283164672143428015!
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> 
> 
> !DSPAM:10175,4fea283164672143428015!