Add docs on how we use support branches #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Raising early to get feedback – still need to work out how this replaces or interacts with the existing guidance on releasing from a support branch. |
36degrees
force-pushed
the
version-control-basics
branch
from
2483554 to
67b8e6b
Compare
36degrees
force-pushed
the
support-branches
branch
from
54300f7 to
9fa75b0
Compare
✅ Deploy Preview for govuk-design-system-team-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
owenatgov
reviewed
Jun 30, 2023
|
As discussed in dev catch up, we should also add:
|
36degrees
force-pushed
the
support-branches
branch
from
9fa75b0 to
c883de4
Compare
36degrees
added a commit
to alphagov/govuk-frontend
that referenced
this pull request
Aug 1, 2023
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 standard docs on publishing releases.
36degrees
force-pushed
the
support-branches
branch
2 times, most recently
from
822d160 to
1aca28c
Compare
owenatgov
reviewed
Aug 8, 2023
36degrees
force-pushed
the
support-branches
branch
from
1aca28c to
58bf69a
Compare
36degrees
added a commit
to alphagov/govuk-frontend
that referenced
this pull request
Sep 20, 2023
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.
36degrees
added a commit
to alphagov/govuk-frontend
that referenced
this pull request
Sep 20, 2023
We’re adding docs on using support branches to our team docs as part of alphagov/design-system-team-docs#21. Update our release docs for v3.x to reflect the fact that this branch is a support branch and to link to the new docs.
36degrees
added a commit
to alphagov/govuk-frontend
that referenced
this pull request
Sep 20, 2023
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 standard docs on publishing releases.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add some docs to illustrate how we can use support branches, building on top of our existing docs on releasing from a support branch.
I've added some illustrations using Mermaid and the very useful Git graph diagram style. There's potential to properly embed it (see alphagov/tech-docs-gem#184) but I figured we should wait and see how useful they are first / how often we use them.