CI: document intended mission for devdeps weekly cron jobs [ci-skip] - #20202

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

Weird, CI still ran.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v7.2.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 8fd38bc2b92aa793571d15a1d1d37f1f765d8471

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #20202: CI: document intended mission for devdeps weekly cron jobs [ci-skip]'

4. Push to a named branch:

git push YOURFORK v7.2.x:auto-backport-of-pr-20202-on-v7.2.x

5. Create a PR against branch v7.2.x, I would have named this PR:

"Backport PR #20202 on branch v7.2.x (CI: document intended mission for devdeps weekly cron jobs [ci-skip])"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v8.0.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 8fd38bc2b92aa793571d15a1d1d37f1f765d8471

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #20202: CI: document intended mission for devdeps weekly cron jobs [ci-skip]'

4. Push to a named branch:

git push YOURFORK v8.0.x:auto-backport-of-pr-20202-on-v8.0.x

5. Create a PR against branch v8.0.x, I would have named this PR:

"Backport PR #20202 on branch v8.0.x (CI: document intended mission for devdeps weekly cron jobs [ci-skip])"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

maybe not worth the (admitedly minor) pain of backporting ?

For v8.0.x, I piggyback this backport in #20204 . Hope you don't mind.

For v7.2.x, I plan to do the same in #20203 after the tox.ini file is fixed. (I can fix it later if it is getting too late for you.)