Update docs for configuring CI email notifications

Secrets are now stored organization-wide rather than per-repository.
This commit is contained in:
Jon Siwek 2020-08-19 11:49:24 -07:00
parent 868004bd00
commit 69cbeb7a1b
4 changed files with 12 additions and 6 deletions

View file

@ -1,4 +1,10 @@
3.3.0-dev.115 | 2020-08-19 11:49:24 -0700
* Update docs for configuring CI email notifications (Jon Siwek, Corelight)
Secrets are now stored organization-wide rather than per-repository.
3.3.0-dev.113 | 2020-08-18 12:10:26 -0700
* GH-467: Catch use of &add_func/&delete_func on IDs without values. (Robin Sommer, Corelight)

View file

@ -1 +1 @@
3.3.0-dev.113
3.3.0-dev.115

@ -1 +1 @@
Subproject commit fd3b48c744c8315abb3aa0ec97581bee5a94cd5c
Subproject commit 32715bf13222610960f9f1969d6b661d59874aa7

View file

@ -39,11 +39,11 @@ so that is instead handled by a separate GitHub Action:
https://github.com/zeek/ci-email-action
The configuration of that GitHub Action is typical: it's just the
``.github/workflows/ci-notification.yml`` file, which set SMTP/mail info
via secrets stored in GitHub for the Zeek repository:
The configuration of that GitHub Action is typical: it's the
``.github/workflows/ci-notification.yml`` file, which sets SMTP/mail info
via secrets stored in GitHub for the Zeek organization:
https://github.com/zeek/zeek/settings/secrets
https://github.com/organizations/zeek/settings/secrets
The particular values used for those are currently from the Zeek project's AWS
Simple Email Service configuration.