On Wed, Dec 01, 2021 at 02:12:29PM +0100, Miro Hrončok wrote: > On 01. 12. 21 0:37, Michael Catanzaro wrote: > > On Wed, Dec 1 2021 at 12:27:35 AM +0100, Emmanuel Seyman > > <emmanuel@xxxxxxxxx> wrote: > > > How do people using this setup prevent people from submitting PR and > > > issues to the Github mirror where they cannot be applied/fixed? > > > > For GNOME we just set up a bot that autocloses every PR. > > Which is rather unpleasant experience for the casual contributor, I must say. There's no perfect solution, but IMHO auto-closing with a friendly comment is less bad than just having the PR ignored forever because no developers look at submissions in the readonly mirror. Note the GNOME auto-closer provides a comment telling the user that the primary repo is on gitlab and pointing them to where it is. Logging into gitlab is simple because it can do SSO with the GitHub identity https://github.com/GNOME/glib/pull/33#issuecomment-650457175 We do much the same in libvirt https://github.com/libvirt/libvirt-python/pull/4#issuecomment-662443409 FWIW, there's no need to write a bot to achieve this - there's a a github action: https://github.com/apps/repo-lockdown you can simply enable for your repos by adding a file: https://github.com/libvirt/libvirt-python/blob/master/.github/workflows/lockdown.yml Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
