[Python-Dev] How is the GitHub workflow working for people?
Matěj Cepl
mcepl at cepl.eu
Wed Feb 21 17:29:56 EST 2018
More information about the Python-Dev mailing list
Wed Feb 21 17:29:56 EST 2018
- Previous message (by thread): [Python-Dev] How is the GitHub workflow working for people?
- Next message (by thread): [Python-Dev] How is the GitHub workflow working for people?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 2018-02-21, 21:49 GMT, Chris Angelico wrote: > Said PEP may also need to mention the possibility of exporting > the history of GitHub issues, in case CPython ever migrates away from > GitHub; I remember that concern being raised when the original > migration was discussed. There are tools for it (e.g., I wrote https://github.com/mcepl/github-issues-export to move issues to Bugzilla, yes I am weird) and it is not that difficult to write something just to get data from GitHub’s all embracing arms. Of course, I am not sure how it would work on really large number of bugs, and it would be necessary to do some postprocessing (changing issue numbers etc.). Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl at ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 God is not worried about my financial situation.
- Previous message (by thread): [Python-Dev] How is the GitHub workflow working for people?
- Next message (by thread): [Python-Dev] How is the GitHub workflow working for people?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list