Changes to db.json should redeploy participate.whatwg.org

[andreubotella]

participate.whatwg.org depends on this repo's db.json to show the list of workstreams, but #164 added the testutil workstream and it is not yet showing up in that list. Changing db.json should probably cause participate.whatwg.org to redeploy, much like it does with whatwg.org.

[annevk]

As I changed db.json this morning I restarted https://github.com/whatwg/participate.whatwg.org/actions/runs/1255401114 in the hope that it does the right thing.

@foolip would fixing this basically involving duplicating the curl call in https://github.com/whatwg/sg/blob/main/.github/workflows/dispatch.yml for this repository? Anything else need to be configured?

[annevk]

It looks like that did not do the trick as https://participate.whatwg.org/agreement does not list Web IDL.

[TimothyGu]

It looks like it's deployed now?

[domenic]

Yeah, I merged one of the dependabot PRs which caused a redeploy that picked up the new db.json.

[domenic]

To fix this we need some way of triggering the DigitalOcean infrastructure to redeploy, as the deploys are currently triggered by them monitoring the commits instead of by GitHub Actions pushing a deploy request or something.

[foolip]

We could use the same setup as here:
https://github.com/whatwg/whatwg.org/blob/3320e88db45f8abc75696a8bfcc4b8827ecc9d08/.github/workflows/build.yml#L9-L12

[domenic]

I don't think this works? This just runs the GitHub Actions, but the GitHub Actions are not what causes a DigitalOcean deploy; DigitalOcean deploys from their side.

[annevk]

So https://spec.whatwg.org/ did end up being updated, but let's reopen this so you and @foolip can verify.

[domenic]

Yeah, participate.whatwg.org is the tricky part. That got deployed, but ironically only because of all the commits trying to set up deployment (i.e., DigitalOcean detected whatwg/participate.whatwg.org@5bf6e71 and thus redeployed, including fetching a new version of db.json).

[annevk]

Oh right, we did not need a participate update this round because we did not fiddle with Workstreams. So I guess one way of doing this would be to create a commit somehow which ends up triggering DigitalOcean at some point.

[domenic]

You do need a participate update to make https://participate.whatwg.org/agreement-status?user=domenic&repo=fs work, actually.