chore: sync OpenAPI spec from flashduty-docs - #59
Closed
github-actions[bot] wants to merge 0 commit into
Closed
Conversation
github-actions
Bot
force-pushed
the
chore/sync-openapi-spec
branch
3 times, most recently
from
August 17, 2026 02:34
13f1af0 to
3c68812
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated sync of the vendored OpenAPI spec from the public
flashduty-docs source of truth, followed by
go generate.openapi/openapi.{en,zh}.jsonrefreshed frommain..gore-emitted to match.Review the diff (new/changed endpoints + regenerated types) before
merging. No PR is opened when upstream has not drifted.