| commit | ba61ff7d2eb6ed697e12abe3688992e85c434b30 | [log] [tgz] |
|---|---|---|
| author | Pedro Kaj Kjellerup Nacht <pnacht@google.com> | Wed Nov 08 08:30:34 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 08 08:35:51 2023 -0800 |
| tree | 628b075603cea6923b1a78c9c2dfe890bfd648d6 | |
| parent | 289d91426ecf609824cca459af8f3bd3a8b1a2c8 [diff] |
Add top-level permissions to cherry-picker and remove-labels.yml Fixes #20086. As described in the issue, this PR adds read-only permissions to bazel's workflows that don't yet have them. This reduces the risk of supply-chain attacks via the project's CI/CD infrastructure. My understanding is that `cherry-picker.yml` does not require any additional permissions since everything done by `bazelbuild/continuous-integration/actions/cherry_picker` uses the declared `GH_TOKEN` instead of the workflow's default `GITHUB_TOKEN`. If I'm mistaken, let me know and I'll happy fix the PR. Closes #20087. PiperOrigin-RevId: 580542813 Change-Id: Ib45164ea8d9c0aa583e91d316ad2b552f3c9b5b7
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
