Explore >> Select a destination
|
You are here 
|
securitylab.github.com | ||
| | | | |
github.blog
|
|
| | | | | Improve your GitHub Actions security posture by securing your source repository, protecting your maintainers, and making it easy to report security incidents. | |
| | | | |
sookocheff.com
|
|
| | | | | This is something I often do but rarely remember the steps for. This post is intended to serve as a reminder for me and anyone else having the same question: how to add an upstream remote git repository. Start by forking the repository you are contributing to and cloning that repository to your local file system. In this example, we will use the Elasticsearch repository and assume you have cloned it locally. | |
| | | | |
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. | |
| | | | |
blog.keikooda.net
|
|
| | | This post is super outdated | ||
