Ran Benita
|
864a2bc0a3
|
ci: use GitHub Actions token instead of `chatops`/`release_notes` secrets
It seems more secure to use the controlled & limited token than an
ambient secret.
|
2021-05-18 16:05:14 +03:00 |
|
Ran Benita
|
6bc6ec323a
|
ci: reduce workflow permissions
Decrease security exposure by restricting what the code executing in the
actions is allowed to do (in terms of GitHub operations).
|
2021-05-18 16:05:14 +03:00 |
Anthony Sottile
|
4da445dc2e
|
Revert "infra: Temporary pin setup-python GH action to v2.1.4"
|
2020-12-18 10:44:20 -08:00 |
antonblr
|
1264404fe7
|
infra: Temporary pin setup-python GH action to v2.1.4
|
2020-12-17 21:01:20 -08:00 |
|
Ran Benita
|
9214e63af3
|
ci: use fetch-depth: 0 instead of fetching manually (#7297)
|
2020-06-02 10:29:36 +03:00 |
|
Ran Benita
|
c66bf59fd5
|
ci: update github action versions, remove outdated comment (#7177)
|
2020-05-08 13:03:51 +03:00 |
Bruno Oliveira
|
a0ea300e96
|
Fix bot trigger event
Issue events don't contain a 'comment' entry:
https://developer.github.com/v3/issues/events/#response-2
Issue comments also contain the original issue body:
https://developer.github.com/v3/activity/events/types/#issuecommentevent
That's why it was triggering even for comments on the issue.
Also changed to startsWith because there's no need to support
the command anywhere in the body IMO.
Fix #6895
|
2020-03-11 09:54:56 -03:00 |
Bruno Oliveira
|
15e1dd0f87
|
Automate release by comment notifications (#6823)
* Automate release by comment notifications
* Only run if @pytestbot is mentioned
|
2020-03-01 14:46:35 -03:00 |