Repository navigation
ci: Run the Flagsmith SDK behavioural spec - #263
Merged
Merged
Conversation
for more information, see https://pre-commit.ci
talissoncosta
previously approved these changes
Oct 21, 2026
talissoncosta
self-requested a review
October 21, 2026 10:45
2 of 4 tasks
bakirFS
approved these changes
Oct 21, 2026
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.
Runs the Flagsmith SDK behavioural spec against this SDK on every pull request and push to
main.sdk-spec/steps.py: one function per SDK step, marked with the Gherkin step text as a comment. It contains only SDK calls and the mapping to the spec's flag shape, so it doubles as a working usage example. It is typed, somypy --strict .covers it.sdk-spec/Dockerfile: builds the SDK from source and runs the steps file under the spec's Python harness, taken from theharnessbuild context. The harness speaks JSON lines over stdin/stdout, so this repo contains no protocol code..github/workflows/sdk-spec.yml: calls the spec's reusable workflow withlanguage: python. The workflow starts a real Flagsmith instance, seeds it through the Admin API and runs the scenarios against the SDK image. It is pinned tov0.3.0.renovate.json: bumps theuses:ref andspec-reftogether.The spec currently covers getting environment flags and getting identity flags with traits.