Skip to content

Commit 08605bb

Browse files
committed
Move support branches docs to team docs
The process for using a support branch is being moved into our team docs as part of alphagov/design-system-team-docs#21. Remove the existing documentation and add a reference to it in our docs on publishing releases. Update those docs to reflect the fact that this branch is a support branch.
1 parent 5f15a4d commit 08605bb

File tree

2 files changed

+5
-130
lines changed

2 files changed

+5
-130
lines changed

docs/releasing/publishing-from-a-support-branch.md

Lines changed: 0 additions & 129 deletions
This file was deleted.

docs/releasing/publishing.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
# Before you publish GOV.UK Frontend
22

3-
Read the docs for [what to do before publishing a release](/docs/releasing/before-publishing-a-release.md) to ensure you are prepared to publish.
3+
This is a support branch, which we use to release additional v4.x versions now that the `main` branch reflects a newer major version.
4+
5+
Make sure you understand how this branch is meant to be used be reading the [documentation on support branches](https://govuk-design-system-team-docs.netlify.app/how-we-work/version-control/support-branches.html#support-branches) in our team docs.
6+
7+
You should also read the docs for [what to do before publishing a release](/docs/releasing/before-publishing-a-release.md) to ensure you are prepared to publish.
48

59
# Publish a new version of GOV.UK Frontend
610

0 commit comments

Comments
 (0)