This came up in https://github.com/scientific-python/docstub/issues/3, that I misinterpreted and thought it was about all the tools we have. I still think it is a good exercise to double check as we may have missed some things in the early days.
(and if it's for updating the policy for new tools/new migrations, that's a sepate thing)
tool name
mainained/admined by SP team instead of individual
This came up in https://github.com/scientific-python/docstub/issues/3, that I misinterpreted and thought it was about all the tools we have. I still think it is a good exercise to double check as we may have missed some things in the early days.
(and if it's for updating the policy for new tools/new migrations, that's a sepate thing)
lazy_loader spin pytest-doctestplus repo_review changelist yaml2ics vault-template devstats upload-nightly-action attach-next-milestone-action action-check-changelogfile action-towncrier-changelog reverse-dependency-testing sync-teams-action circleci-artifacts-redirector-action MeeseeksDev / Lumberbot (App)