FilesExpand file tree

main

/

comment-release-note-info.yml

Copy path

View runs

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

32 lines (27 loc) · 1.49 KB

main

/

comment-release-note-info.yml

Copy path

Top

File metadata and controls

• Code
• Blame

32 lines (27 loc) · 1.49 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

name: Comment on release note changes

# Prompts contributors to request technical review for release note changes.

on:

pull_request:

types:

- opened

paths:

- data/release-notes/enterprise-server/**

- .github/workflows/comment-release-note-info.yml

permissions:

contents: read

pull-requests: write

jobs:

comment:

# Skip release-controller patch PRs and public-repo PRs.

if: github.event.pull_request.user.login != 'release-controller[bot]' && github.repository == 'github/docs-internal'

runs-on: ubuntu-latest

steps:

- uses: peter-evans/create-or-update-comment@e8674b075228eee787fea43ef493e45ece1004c9

with:

issue-number: ${{ github.event.pull_request.number }}

body: |

Thank you for updating our GitHub Enterprise Server release notes. Please request a technical review for your changes. Once the technical review is complete, a member of the `docs-content-enterprise` team will review your changes.

- If the change is urgent, post in `#docs-content-enterprise` on Slack.

- Review the [style guide for release notes](https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#release-notes).

- If you're updating or adding a note, add a datestamp in the format `[Updated: YYYY-MM-DD]`.

- If you're removing a note, add an [Errata](https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#errata) section with details of the change.