Terence Tuhinanshu

The self-hosted runner does not need to be accessible from the internet, as long as it can access the internet itself, since the [GitHub Actions Runner application long-polls GitHub](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github) for...

This could be problematic: GitHub recommends we [use self-hosted runners with only private repos](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security), because forks of public repos would run the same jobs. Wonder if we could do some...

May have to add a CODEOWNERS file too, especially to [protect any changes that could be made to the workflows](https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-codeowners-to-monitor-changes) file.

🤔 > **Self-hosted runners** for GitHub do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow. > >...

Some more details on [workflows from forks](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflows-in-forked-repositories): > Workflows don't run in forked repositories by default. You must enable GitHub Actions in the **Actions** tab of the forked repository. >...

Yes sorry, this is still not implemented.

Yes, good catch.

Regarding the zoom buttons stacking, see discussion here: https://github.com/WikiWatershed/model-my-watershed/issues/1782#issuecomment-293294147

Noticing that the average job runtime is going up, seems to be reset with every production deployment: ```sql SELECT DATE(created_at), EXTRACT(EPOCH FROM AVG(delivered_at - created_at)) AS avg_seconds FROM core_job WHERE...

Another version of the query above, but looking at p75 and p95 metrics instead of the average: ```sql WITH query_durations AS ( SELECT DATE(created_at), EXTRACT(EPOCH FROM delivered_at - created_at) AS...