Repository navigation
docs: add new-navigation-banner to developer-tools classic pages (DOCT-2626 Phase B) - #1580
Merged
Merged
Conversation
…ges (DOCT-2626 Phase B)
Prepends `{% include "<relative>/.gitbook/includes/new-navigation-banner.md" %}`
after the YAML frontmatter on every page in this section whose frontmatter
declares `nav_context: classic`.
Filter: `grep -l '^nav_context: classic$'` across the section.
Scope this PR: 113 files.
Depends on the banner include file in main (PR #1577, merged).
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
mihaisau-snyk
approved these changes
Aug 4, 2026
VeronicaSnyk
approved these changes
Aug 4, 2026
…t-developer-tools # Conflicts: # developer-tools/integrations/snyk-essentials-integrations-reference.md
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
Adds
{% include "<relative>/.gitbook/includes/new-navigation-banner.md" %}to every page indeveloper-tools/whose frontmatter declaresnav_context: classic. The include renders an info hint linking to Navigating Snyk (from PR #1577, merged).Files changed: 113.
Filter used
Untouched:
nav_context: newornav_context: agnostic.nav_contextkey.Test plan
https://docs.snyk.io/getting-started/navigating-snyk.git diff --statmatches the expected 113 files, exactly two-line insertion each.Generated by Claude Code
Note
Low Risk
Documentation-only, repeated include wiring with no product or auth logic changes.
Overview
Phase B (DOCT-2626) rolls the shared GitBook include
new-navigation-banner.mdonto 113developer-tools/pages that declarenav_context: classic, placing it immediately after the frontmatter and before the page title.Each page gets the same two-line insertion: a blank line plus
{% include "<relative>/.gitbook/includes/new-navigation-banner.md" %}, with the relative path adjusted for folder depth. Pages markednav_context: new,agnostic, or withoutnav_contextare unchanged.Readers on classic developer-tools docs should see the standard info banner (linking to Navigating Snyk) above the first heading, consistent with other spaces that already use this include.
Reviewed by Cursor Bugbot for commit b8fb9b7. Bugbot is set up for automated code reviews on this repo. Configure here.