Bilby development migration plan

[ColmTalbot]

This issue describes the requirements and plan for migrating bilby development from the LIGO GitLab to Github.

Requirements

• CI working on GitHub (Add GitHub action testing #24)
• Move existing mirror to bilby-dev
• Sort branches (master vs GitHub main)
  • Change default when everything is done
• Migrate pull requests
  • ~~write a documentation page/issue describing how to change the remote to GitHub ~~
  • ~~Do we need mapping from LIGO users to GitHub users? ~~
  • Dry run hit request limit.
    • Can skip closed/merged MRs
• ~~Migrate issues ~~
  • ~~Use a robot account https://docs.github.com/en/authentication/connecting-to-github-with-ssh/managing-deploy-keys#machine-users ~~
  • ~~Use a obfuscated username for the mapping to avoid tags ~~
• Migrate labels
• Migrate milestones
• Documentation - change how it is deployed (readthedocs vs github pages)
  • Currently permissions issue in deployment
  • Update URLs etc in docs
• Release process
  • Added to PyPI trusted reviewers
  • PR to add workflow
• Permissions (adding reviewers/contributors)
  • Pending checks
• Approval rules
• ~~Place for LVK-specific issues ~~
  • Point people to bilby_pipe for confidential issues
• ~~Update references everywhere ~~
  • ~~Bilby reference (MAINT: migration updates #36) ~~
  • ~~Bilby_pipe (https://git.ligo.org/lscsoft/bilby_pipe/-/merge_requests/614) ~~
• Fix DOI
  • Added zenodo hook, needs new release to trigger. Unsure about old releases
  • If we make releases by hand they should automatically push to zenodo
• Update container registry
  • Colm will do
  • .devcontainer - we may want specifications for minimal and GW versions Add devcontainer file #843
  • Should just require updating paths - https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry
• Document ‘sharp bits’ compared to GitLab/general migration guide (MAINT: add gitlab to github migration guide #40)
  • Squash and merge for PRs
  • Managing releases/changelog
  • Updating remotes
  • Migrating MRs/issues
• Authors
  • ~~ORCID/citation cff ~~
• Coverage badge
• Direct people to github from gitlab
• ~~Releases ~~
  • Make releases to trigger zenodo push
  • Disable other CI jobs for releases temporarily

[mj-will]

I've migrated the labels and milestones, I'll start the issues later today.

[mj-will]

And that's the issue transfer complete.