docs(gherkin-to-asciidoc): add multi-project example demonstrating the indexing modes - #100
Merged
Merged
Conversation
…e indexing modes Adds off/feature/scenario/all sub-projects, each with byte-for-byte identical copies of the same two feature files (features-auth, features-billing), differing only in their indexing configuration - so running generateFeatureDocs at the root and comparing the four generated reports (and the numbering baked into each sub-project's own copy of the source files) shows exactly what each mode does. Pinned to gherkin-to-asciidoc = 2.0.0 in gradle/libs.versions.toml, the version indexing is expected to release as; verified locally against the plugin's own source (via a temporary includeBuild, since removed) before pinning. Won't build against the Gradle Plugin Portal until that version is actually released, matching this repository's usual process for examples of an unreleased feature. Adds a matching example-gherkin-to-asciidoc-indexing-build.yml CI workflow, mirroring the other gherkin-to-asciidoc examples'. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Aug 5, 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.
Summary
off/feature/scenario/allsub-projects, each starting from byte-for-byte identical copies of the same two feature files (features-auth,features-billing), differing only in theirindexingconfiguration - so runninggenerateFeatureDocsat the root and comparing the four generated reports (and the numbering baked into each sub-project's own copy of the source files) shows exactly what each mode does.example-gherkin-to-asciidoc-indexing-build.ymlCI workflow, mirroring the othergherkin-to-asciidocexamples'.Notes
gherkin-to-asciidoc = 2.0.0ingradle/libs.versions.toml- now the actual released version (see feat(gherkin-to-asciidoc)!: add indexing DSL property to number features and scenarios #99), resolved from the Gradle Plugin Portal like the other examples.actionlintclean on the new workflow (and repo-wide).