Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
Looking at https://lwn.net/Articles/857791/, GCC does not require contributors listed in MAINTAINERS to sign every commit. People probably do forget occasionally to do this, so maybe it's cleaner to automatically opt-in...
### Description This adds tests using [dredd](https://dredd.org). 1. Builds the spec that only includes APIs with `x-tested`. This is a new feature of the merger than can be extended in...
## What/Why ### What are you proposing? Add a CHANGELOG like in other projects and a workflow that ensures that a CHANGELOG is present with every PR. ### What users...
### Is your feature request related to a problem? It's unclear whether the generator worked. ``` $ npm run merge -- $ROOT_PATH $OUTPUT_PATH > [email protected] merge > ts-node merger/merge.ts ../spec...
## What/Why ### What are you proposing? Coming from https://github.com/opensearch-project/opensearch-api-specification/pull/271#issuecomment-2088669972, we don't actually know whether the specs authored here are correct. Add integration tests that exercise these specs. ### What...
### Is your feature request related to a problem? Coming from https://github.com/opensearch-project/opensearch-api-specification/pull/271 where we reordered a DELETE method. ### What solution would you like? A linter that orders methods (probably...
### Is your feature request related to a problem? Coming from https://github.com/opensearch-project/opensearch-api-specification/pull/264 we removed quotes around YAML text values which are unnecessary. ### What solution would you like? A linter...
## What/Why ### What are you proposing? All source code should have an SPDX license header. ### What users have asked for this feature? Standard org-wide practice. ### What problems...
### Is your feature request related to a problem? The spec repo should be 100% of specs that ship with OpenSearch and kept up-to-date. ### What solution would you like?...
### Is your feature request related to a problem? The API coverage workflow comments with something like "API specs implemented for 247/649 (38%) APIs.". This doesn't say what changed. ###...