  hashicorp-tsccr[bot]andhashicorp-tsccr[bot]
|
0194d839b0
|
Result of tsccr-helper -log-level=info -pin-all-workflows . (#12507)
Co-authored-by: hashicorp-tsccr[bot] <hashicorp-tsccr[bot]@users.noreply.github.com>
|
2023-07-19 13:20:14 -04:00 |
|
|
hashicorp-tsccr[bot]andhashicorp-tsccr[bot]
|
3ac1179841
|
Result of tsccr-helper -pin-all-workflows . (#12381)
Co-authored-by: hashicorp-tsccr[bot] <hashicorp-tsccr[bot]@users.noreply.github.com>
|
2023-04-27 14:55:22 -04:00 |
|
 Bryce Kalow
|
954285632d
|
fix: use newer node for check-plugin-docs (#11893)
|
2022-07-21 11:23:29 -04:00 |
|
  Wilken Riveraandneilnaveen
|
cc5898022a
|
update action permissions (#11837)
* chore: Set permissions for GitHub actions
Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much.
- Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions
https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs
[Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/)
Signed-off-by: neilnaveen <[email protected]>
* Update permissions for newly added actions
* Remove deleted actions
Co-authored-by: neilnaveen <[email protected]>
|
2022-06-14 12:08:39 -04:00 |
|
|
Bryce Kalow
|
1c0d3ad93d
|
website: website source code / content split (#11716)
|
2022-04-20 15:51:18 -05:00 |
|
 Zach Shilton
|
b780da5750
|
website: run plugin docs check also on schedule
|
2021-03-20 21:59:34 -04:00 |
|
|
Zach Shilton
|
26a572270d
|
website: add github action to flag plugin-docs issues
|
2021-03-18 12:25:36 -04:00 |
|