Skip to content

Commit cf3f14f

Browse files
committed
fix: correct frontmatter and broken links
- Fix versions field format from '- ghes' to 'ghes: *' - Fix absolute URLs to relative paths - Use data variable for product name in intro and headers
1 parent a5028aa commit cf3f14f

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

content/admin/overview/about-upgrades-to-new-releases.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: About upgrades to new releases
33
shortTitle: About upgrades
4-
intro: Learn about how features and bug fixes are added to GitHub Enterprise Server through new releases.
5-
versions:
6-
- ghes
4+
intro: 'Learn about how features and bug fixes are added to {% data variables.product.prodname_ghe_server %} through new releases.'
5+
versions:
6+
ghes: '*'
77
type: overview
88
topics:
99
- Enterprise
@@ -33,7 +33,7 @@ Release candidates are _proposed_ feature releases, with a complete feature set.
3333

3434
For performance, stability, and security reasons, follow these guidelines when testing release candidates.
3535

36-
As you test a release candidate, please provide feedback by contacting support. See [AUTOTITLE](https://github.com/github/docs/blob/main/support).
36+
As you test a release candidate, please provide feedback by contacting support. See [AUTOTITLE](/support).
3737

3838
Each new release candidate adds bug fixes for issues found in prior versions. When the release is ready for widespread adoption, {% data variables.product.company_short %} publishes a stable feature release.
3939

@@ -54,25 +54,25 @@ Between feature releases, you can benefit from patch releases, which:
5454
| **Release Candidate** | Testing new features | Minimal | Test/staging only |
5555
| **Patch** | Bug fixes between features | <5 minutes | Production ready |
5656

57-
## Upgrading GitHub Enterprise Server
57+
## Upgrading {% data variables.product.prodname_ghe_server %}
5858

5959
There are two ways to upgrade {% data variables.product.prodname_ghe_server %}:
6060

6161
### Option 1: New instance
6262
Set up a **completely new {% data variables.product.prodname_ghe_server %} instance** and configure the instance however you like.
6363

6464
**Steps:**
65-
- See [AUTOTITLE](https://github.com/github/docs/blob/main/admin/installation/setting-up-a-github-enterprise-server-instance)
66-
- Then see [AUTOTITLE](https://github.com/github/docs/blob/main/admin/configuration/configuring-your-enterprise)
65+
- See [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance)
66+
- Then see [AUTOTITLE](/admin/configuration/configuring-your-enterprise)
6767

6868
### Option 2: Existing instance upgrade
6969
Upgrade your **existing instance** to a new release.
7070

7171
**Steps:**
72-
- See [AUTOTITLE](https://github.com/github/docs/blob/main/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process)
72+
- See [AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process)
7373

7474
## Further reading
7575

7676
- [{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %}) in the `github/roadmap` repository
77-
- [AUTOTITLE](https://github.com/github/docs/blob/main/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process)
78-
- [AUTOTITLE](https://github.com/github/docs/blob/main/admin/installation/setting-up-a-github-enterprise-server-instance)
77+
- [AUTOTITLE](/admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process)
78+
- [AUTOTITLE](/admin/installation/setting-up-a-github-enterprise-server-instance)

0 commit comments

Comments
 (0)