Skip to content

Commit

Permalink
docs(releasing): add step for announcing on Slack (#12751)
Browse files Browse the repository at this point in the history
Signed-off-by: Anton Gilgur <[email protected]>
(cherry picked from commit 9d8b38e)
  • Loading branch information
Anton Gilgur committed May 11, 2024
1 parent 8bfffcf commit 6c52b5e
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion docs/releasing.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,11 @@ you can approve it, enable auto-merge, and then run the following to force trigg
git branch -D create-pull-request/changelog
git fetch upstream
git checkout --track upstream/create-pull-request/changelog
git commit -s --allow-empty -m "docs: Force trigger CI"
git commit -s --allow-empty -m "chore: Force trigger CI"
git push upstream create-pull-request/changelog
```

## Announce on Slack

Once the changelog updates have been merged, you should announce on our Slack channels, [`#argo-workflows`](https://cloud-native.slack.com/archives/C01QW9QSSSK) and [`#argo-announcements`](https://cloud-native.slack.com/archives/C02165G1L48).
See [previous](https://cloud-native.slack.com/archives/C02165G1L48/p1701112932434469) [announcements](https://cloud-native.slack.com/archives/C01QW9QSSSK/p1701112957127489) as examples of what to write in the patch announcement.

0 comments on commit 6c52b5e

Please sign in to comment.