Filter environment variables when building with Bazel #7846
Annotations
1 error and 2 warnings
Check
The message 1 is invalid:
* The subject must start with a verb in imperative mood, but it started with: "Filter". Whether the word is in imperative mood is determined by whitelisting. The general whitelist is available at https://github.com/mristin/opinionated-commit-message/blob/master/src/mostFrequentEnglishVerbs.ts. You can whitelist additional verbs using "additional-verbs" input to your GitHub action (currently one or more additional verbs were thus specified). Moreover, you can also whitelist additional verbs in a file given as "path-to-additional-verbs" input to your GitHub action (currently no whitelist file was specified). Please check the whitelist and either change the first word of the subject or whitelist the verb.
The original message was:
Filter environment variables when building with Bazel
In order for Xcode builds to work with custom environment variables you need to use `xcodeproj.bazel_env`. This just takes the extra step of filtering out all other environment variables, ensuring more analysis cache hits. You can already do this in your own `tools/bazel`, but now people can get the benefit regardless.
This change is needed for shared outputs bases to be performant.
|
The following actions uses node12 which is deprecated and will be forced to run on node16: mristin/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: mristin/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Loading