[Twisted-Python] Suggested plan for GitHub migration

Tristan Seligmann mithrandi at mithrandi.net
Tue Dec 1 00:35:15 MST 2015


On Mon, 30 Nov 2015 at 16:50 Amber "Hawkie" Brown <hawkowl at atleastfornow.net>
wrote:

> The migration will have a handful of policy changes that we will have to
> resolve -- such as ensuring that all merges have a topfile -- which aren't
> possible under a GitHub based system.


You could make master/trunk/whatever a protected branch, and have a
required status check for this, but that would require some external CI
thing that actually performs the status check.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://twistedmatrix.com/pipermail/twisted-python/attachments/20151201/192c4fde/attachment.html>


More information about the Twisted-Python mailing list