Skip to content

Conversation

shivani170
Copy link
Contributor

@shivani170 shivani170 commented Sep 30, 2025

Description

Task: Nested Navigation Routing

Fixes https://github.com/devtron-labs/sprint-tasks/issues/2619

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas

vivek-devtron
vivek-devtron previously approved these changes Oct 1, 2025
@shivani170 shivani170 changed the title chore: nested breadcrumb in Policy & configurataion feat: nested breadcrumb in Policy & configurataion Oct 7, 2025
Copy link

github-actions bot commented Oct 7, 2025

Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n

@github-actions github-actions bot added PR:Issue-verification-failed PR:Issue-verification-failed and removed PR:Ready-to-Review PR:Ready-to-Review labels Oct 7, 2025
@shivani170 shivani170 self-assigned this Oct 7, 2025
@github-actions github-actions bot added PR:Ready-to-Review PR:Ready-to-Review and removed PR:Issue-verification-failed PR:Issue-verification-failed labels Oct 7, 2025
Copy link

sonarqubecloud bot commented Oct 7, 2025

@shivani170 shivani170 merged commit 06d27e3 into kubecon-2025 Oct 7, 2025
9 of 10 checks passed
@shivani170 shivani170 deleted the feat/nested-navigation-route branch October 7, 2025 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR:Ready-to-Review PR:Ready-to-Review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants