Migrate Python CFFI to Github
We've been talking about moving this project to the python-cffi
Github org for awhile now, and last I checked @arigo was cool with it. This will make doing CI and releases via GHA much easier than the manual git-hg remote sync dance I've been doing for the past couple years. We've already got some unreleased changes, and more are needed soon for Python 3.12 support anyway, so seems like a good time to rip off this particular band-aid. The git-hg interop tools I've been relying on to move things to the staging Github repo for CI/releases seem to be rotting quickly, which also adds a bit more urgency.
@mattclay has agreed to help with the migration- a quick checklist off the top of my head:
-
decide target repo name- IMO python-cffi/python-cffi
is the least confusing and minimize confusion and fork name collisions with the existingcffi/cffi
project -
decide on issue migration (recent open, all, none? standard Gitlab->GH migration tools didn't work on heptapod last I tried) -
depending on results of --^ should we make any attempt to rewrite issue/MR numbers in Git commit messages to match GH? -
decide which branches to preserve in Github (eg, ditch some/all MR feature branches?) -
once --^ have been resolved, final code migration to Git and push to new repo -
enable GHA CI on new repo -
fix up Apple Silicon aarch64 builds from new repo (temporarily via existing hacky CI, or if GH-hosted aarch64 beta is available)
(optional, but much easier once we're on GH)
-
enable commit-free release process via setuptools_scm
-
enable OIDC publishing to PyPI -
enable native aarch64 CI for Linux/Windows