/explore
|
You are here 
|
til.simonwillison.net | ||
| | | | |
huey.xyz
Triggering a GitHub action from a git push from another GitHub action. This site is a static site with a deployment pipeline that comprises various daisy-chained GitHub actions. For example, there is a GitHub action that checks my BookWyrm orreadi.com profile periodically, and updates a JSON file in the GitHub repository for this site if there are changes to the books... |
|
| | | | | ||
| | | | |
shot-scraper.datasette.io
[AI summary] shot-scraper is a command-line utility for taking automated screenshots of websites and running tests on web browsers. |
|
| | | | | ||
| | | | |
fanrongbin.com
[AI summary] This article presents a GitHub Actions workflow that automatically downloads, takes character samples, and subsets various Chinese, Japanese, and Korean fonts for a website. |
|
| | | | | ||
| | | | |
code.dblock.org
The OpenSearch API specification is authored in OpenAPI and used to auto-generate OpenSearch language clients. I wanted to know how much of the API was described in it vs. the actual API implemented in the default distribution of OpenSearch that includes all plugins. To do so, I have exposed an iterator over REST handlers in OpenSearch core, and wrote a plugin that rendered a very minimal OpenAPI spec at runtime. All that was left was to compare the manually authored OpenAPI spec in opensearch-api-specification to the runtime one, added in opensearch-api-specification#179. The comparison workflow output a total and relative number of APIs described. |
|
| | | |||
