Automate (some) scripts with GitHub Actions

[claremacrae]

Candidate tasks:

• Updating theme download counts
  • Part of Updating Extensions
• Adding new theme, plugin and people pages
  • Part of Updating Extensions
• Generating the MOCs
  • Updating MOC files
• Running the Python tests
  • Testing Python Code with Approval Tests
• Turn off progress display on the slower scripts - they make the logs hard to read
• Make it create a PR
• Decide which things happen only on main - and adjust the YAML to implement that
• Or decide what will trigger the job that creates commits - maybe a nightly cron job?
  • update_hub will only run on manual trigger, and only on main branch
  • The other two will run on pushes and PRs
  • So the workflow for updating releases will be:
    • Trigger update_hub
    • 3 minutes later, review and accept PR
    • Pull the changes to your branch
    • Run update_releases.py with --overwrite
    • Review and push edits
  • Over time, we should be eventually able to add the --overwrite step to update_hub.yml
• Finish addressing comments from code review
• Remove push and pr triggers on update_hub

After Merge

• Moved to Review the pages in the vault that describe the GutHub actions and the steps for updating content #278
  • The steps for updating releases will be much simpler, as most of the steps will now be automated
  • I (Clare) have some shelved notes for this, in my fork
• Adjust the branch protection to enable "checks must have passed on protected branch" - this will then show any errors nice-and-obviously in PRs
• Moved to Add build status badges on front page, before the H1 #280

Defer to later on

Probably add new issues for these, if they don't exist already

• Moved to Implement automated sorting of some lists on links #282
• Moved to Consider automating the update of "Structure of the Community Vault" IN CONTRIBUTING #281

[claremacrae]

The background to this is written up at:
03.03 Scripts and Automation GitHub Actions for the Hub

[claremacrae]

I'm doing this on my fork of this repo for now - and the logs are available

[claremacrae]

Progress: I've now got meaningful output from an intentionally failing test:

https://github.com/claremacrae/obsidian-hub/runs/4707955213?check_suite_focus=true#step:5:45

[claremacrae]

Theme download counts now get updated automatically:

[claremacrae]

@argenos This is the GitHub Action I'm using to create a PR...

There's a lot to think about its behaviour:
https://github.com/peter-evans/create-pull-request

[claremacrae]

Reopening as there are a few more checklist items to do, in the description of this issue.

@argenos If not already done, when you have a mo, please could you adjust the branch protection to enable "checks must have passed on protected branch"?

[claremacrae]

Oh yes, could you also cherry-pick the README Heading changes some time? Thanks!

[claremacrae]

Oh yes, could you also cherry-pick the README Heading changes some time? Thanks!

Forgot to ping @argenos

[claremacrae]

All the remaining actions here have been moved to separate issues, so this can now be closed.