Skip to content

GHES stacked pull requests landing page links to unavailable content #46289

Open

Description

@haiderbhanpurawala

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/enterprise-server@3.20/pull-requests/how-tos/stacked-pull-requests

What part(s) of the article would you like to see updated?

The stacked pull requests landing page is accessible under the GitHub Enterprise Server 3.20+ documentation. However, the feature is not currently available for GitHub Enterprise Server.

The links in the Recommended section are rewritten as GitHub Enterprise Server 3.20 URLs, but the linked articles are not published for that version. As a result, selecting any of these recommendations returns a 404 page.

This makes it appear that stacked pull requests are supported on GitHub Enterprise Server and creates confusion for users.

Expected outcome:

  • Preferably, prevent the stacked pull requests landing page from being published for GitHub Enterprise Server.

  • Alternatively, add a prominent statement such as: “Stacked pull requests are not currently available for GitHub Enterprise Server.”

  • Ensure the Recommended section does not contain links that lead to 404 pages.

Additional information

Reproduction steps:

  1. Open https://docs.github.com/en/enterprise-server@3.20/pull-requests/how-tos/stacked-pull-requests.

  2. Select any article under Recommended.

  3. Observe that the resulting GitHub Enterprise Server 3.20 URL returns a 404.

The public documentation source uses the pr-stacks feature flag. Its version definition currently includes fpt and ghec, but no GitHub Enterprise Server version:

https://github.com/github/docs/blob/main/data/features/pr-stacks.yml

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Oct 13, 2026
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions