Add downstream migration guide for the explicit-feature model#101
Merged
Conversation
nradakovic
requested review from
AlexanderLanin,
antonkri and
dcalavrezo-qorix
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
Adds downstream-facing migration documentation for adopting the toolchains under Bazel’s explicit-feature model (no_legacy_features), and links that guidance from existing top-level documentation so consumers can find it quickly.
Changes:
- Adds a new downstream migration guide describing explicit feature management and common migration scenarios.
- Links the migration guide from the README, toolchain feature catalog, and extension API docs.
- Adds brief cross-references to steer readers to the migration guide when
no_legacy_featuresis relevant.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| README.md | Adds a new documentation link entry for the migration guide. |
| docs/migration_guide.md | New guide describing behavior changes under no_legacy_features and migration approaches. |
| docs/features.md | Adds a prominent pointer to the migration guide near the top of the feature catalog. |
| docs/extension_api.md | Adds a short “Migrating Downstream Workspaces” section linking to the guide. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Publishes docs/migration_guide.md explaining the impact of no_legacy_features, which previously implicit behaviors are now opt-in, and how consumers restore them explicitly via target/package features, --features flags, opt-in features, and the extra_*_flags toolchain attributes. Links the guide from the README, features.md, and extension_api.md. resolves #81
nradakovic
force-pushed
the
nira_migration_docs
branch
from
9f428cf to
171044c
Compare
antonkri
approved these changes
Jul 15, 2026
github-project-automation
Bot
moved this from In Progress
to Done
in INF - Infrastructure Community
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.
Publishes docs/migration_guide.md explaining the impact of no_legacy_features, which previously implicit behaviors are now opt-in, and how consumers restore them explicitly via target/package features, --features flags, opt-in features, and the extra_*_flags toolchain attributes. Links the guide from the README, features.md, and extension_api.md.
resolves #81