Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab Docs GitLab Docs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 185
    • Issues 185
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab DocsGitLab Docs
  • Merge requests
  • !498

Allow for separate per-project navigation

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Jacques Erasmus requested to merge 409-per-project-navigation into master Jul 30, 2019
  • Overview 25
  • Commits 7
  • Pipelines 11
  • Changes 4

This adds the ability to have separate navigations per project.

With these changes, a new navigation menu can be created by simply creating a new <project>-nav.yaml file for the respective project.

The navigation will be generated from the <project>-nav.yaml if it exists and will fall back on default-nav.yaml if it does not exist.

Preview

Screen_Recording_2019-07-31_at_08.55.49.2019-07-31_08_57_23

Closes #409 (closed)

Edited Jul 31, 2019 by Jacques Erasmus
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: 409-per-project-navigation