/explore
|
You are here 
|
til.simonwillison.net | ||
| | | | |
simonwillison.net
|
|
| | | | | ||
| | | | |
andrewlester.net
Deploying a SvelteKit application to GitHub Pages. |
|
| | | | | ||
| | | | |
davquar.it
A GitHub Action is the automatic execution of a job, after a specified trigger on a GitHub repository. For example, let's say that we want to run a linter on each new commit, we can create a GitHub action to do it. In this post we'll see a workflow to automatically deploy a Hugo site on GitHub Pages. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
