add status page

[oliver-sanders]

• Add a JSON file mapping component branches to meta releases. This will save us having to maintain this list for each of the components individually.
• Add a status page generated from this to give better visibility of failures.

This can be used to automatically pick compatible Cylc versions for installation for CI in the Cylc component repositories via release-actions - https://github.com/cylc/release-actions/pull/46

[oliver-sanders]

For some reason this action doesn't show up on my fork when pushed to master - https://github.com/oliver-sanders/cylc-admin/actions

Not sure why, I've probably done something badly wrong, not sure how to test the action without it.

[MetRonnie]

Do you need to enable it in the repo settings?

[oliver-sanders]

I think it's enabled?

[MetRonnie]

Only thing I can think of is to push a dummy commit to master to try and get it to trigger the Actions workflow for the first time

[oliver-sanders]

Good idea, sadly didn't do the trick.

[oliver-sanders]

It's not a complex action and the script can be tested manually so can always fix in situ if needed.

[MetRonnie]

# Note: This action deletes its previous commits so the nightly build history
# is not preserved and does not require housekeeping.

Doesn't look like it is doing this to me

I see you've now removed that comment, but isn't self-housekeeping desirable?

[oliver-sanders]

isn't self-housekeeping desirable?

That would require force pushing.

That comment was accidentally copied from a cylc-doc action where each "push" contains a complete build of the docs which is substantial. Each of the commits here is just a couple of lines of JSON and Markdown so much less concerning.

[oliver-sanders]

IMO having nightly commits piling up would be a bit messy,

We shouldn't actually get "nightly" commits because the status page should only change when the branches get updated. Otherwise the page should build exactly the same every time so there will be nothing to commit, so nothing will get pushed up. We should only get one commit each time we change the branches, typically once per minor release of cylc-flow which will be a manageable number.

I think workflow should probably skip the "push changes" part if there's nothing to commit incase the commit or push return non-zero because of this?

Note, the cron schedule isn't actually necessary here, the only reason I added it was to have some indication if the action breaks.