Explore >> Select a destination
|
You are here 
|
shipit.dev | ||
| | | | |
mtsknn.fi
|
|
| | | | | Or any other automatic periodic builds. I'm using daily builds to automatically publish scheduled blog posts on my Eleventy site. | |
| | | | |
humanwhocodes.com
|
|
| | | | | When you want your JavaScript code to access all of the data from a previous GitHub Actions workflow step. | |
| | | | |
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. | |
| | | | |
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... | ||
