Using GitHub Issues for Python

Posted May 23, 2018 7:00 UTC (Wed) by nirbheek (subscriber, #54111)
In reply to: Using GitHub Issues for Python by vstinner
Parent article: Using GitHub Issues for Python

That PEP and the resolution (in 2016) were for repository hosting, not for issue tracking.

to post comments

Using GitHub Issues for Python

Posted May 23, 2018 8:50 UTC (Wed) by vstinner (subscriber, #42675) [Link] (2 responses)

Moving issues to GitHub follows the previous PEP which moved the code and pull requests. I don't think that it would make sense to use GitHub for code and GitLab for issues. For example, having pull requests and issues at the same place allows to get globally unique identifiers (#xxx for issues and pull requests). But I don't know how to get links on "bpo-xxx" identifiers (links to bugs.python.org issues).

A few years ago, bugs have migrated from Sourceforge to Roundup (bugs.python.org) and we were able to keep the identifiers. I'm not sure that it's doable here.

Using GitHub Issues for Python

Posted May 23, 2018 9:09 UTC (Wed) by nirbheek (subscriber, #54111) [Link] (1 responses)

Sure, I don't mean split your workflow across two different instances. I mean that GitLab has exactly the same workflow as GitHub w.r.t. pull requests, and the UI is very similar too (+ has a lot more features, has a more usable mobile UI, better command-line integration, etc). So they should seriously evaluate GitLab for issue tracking and wiki and not just go with GitHub because it's easier and because Guido likes it.

Using GitHub Issues for Python

Posted May 23, 2018 9:23 UTC (Wed) by vstinner (subscriber, #42675) [Link]

It took two years to migrate Python code to GitHub. It's not just code, it's also the documentation for developers, the tooling, the integration of all tools, etc. I don't think that anyone wants to move to GitLab right now.