release docs: update patch release request template (#40036)

This commit is contained in:
leo 2022-08-09 09:41:36 -04:00 committed by GitHub
parent fd4d62265d
commit 67bc44df92
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 4 deletions

View File

@ -1,12 +1,14 @@
---
name: Request patch release
about: Sourcegraph teams, use this issue to propose a patch release or include your changes in a patch release.
title: ''
title: '$MAJOR.$MINOR.$PATCH patch release request'
labels: 'release-guild,patch-release-request'
assignees: ''
---
<!-- Update the title according to the relevant patch release -->
@sourcegraph/release-guild I am requesting the following commits be included in a patch release. They are already merged into `main`:
- <!-- LINK TO EXACT MERGED COMMITS HERE -->
@ -52,8 +54,8 @@ I have read [when and why we perform patch releases](https://handbook.sourcegrap
- [ ] Change `upcomingRelease` to the current patch release
- [ ] Change `previousRelease` to the previous patch release version
- [ ] Change `releaseDate` to the current date (time is optional) along with `oneWorkingDayAfterRelease` and `threeWorkingDaysBeforeRelease`
- [ ] Change `captainSlackUsername` and `captainGitHubUsername` accordingly
- [ ] `yarn release tracking:issues`
- [ ] Change `captainSlackUsername` and `captainGitHubUsername` to the patch captain's
- [ ] Run `yarn release tracking:issues` on `main`
- [ ] Add the listed commits alongside a link to this issue to the generated [release tracking issue](https://github.com/sourcegraph/sourcegraph/issues?q=is%3Aissue+label%3Arelease-tracking+)
- [ ] **Comment and close this issue once the relevant commit(s) have been cherry-picked into the release branch**.

View File

@ -4,7 +4,7 @@ Get started and create your first [code insight](index.md) in 5 minutes or less.
## Introduction
In this guide, you'll create a Sourcegraph code insight that tracks the number of `TODOS` that appear in parts of your codebase.
In this guide, you'll create a Sourcegraph code insight that tracks the number of `TODOs` that appear in parts of your codebase.
For more information about Code Insights see the [Code Insights](index.md) documentation.