Alex Faxå

Nope, I worked around it with a manual merge.

I think I'm also hit by this. I am using the prometheus-operator helm chart (version 0.32.0). ``` apiVersion: monitoring.coreos.com/v1 kind: PodMonitor metadata: name: fluentd-metrics labels: prometheus: kube-prometheus spec: podMetricsEndpoints: -...

Thanks Frederic. Turns out my problem was caused by running prometheus-operator Helm chart 6.11.0 when PodMonitor support was added in 6.12.0. And Helm ignores all unknown values (`podMonitorNamespaceSelector` and `podMonitorSelector`)...

Bumping this as I do see recent PR being merged.

I spent some time looking at the repro in https://github.com/googlecloudrobotics/core/pull/268 but could not find anything out. I agree the plugin is installed. For reference, if trying the "old" way e.g....

Just remove that variable. It is not used. Should probably send a PR.

> Edit: I see that `github.event.pull_request.merge_commit_sha` is `null` for `pull_request_target` event: https://github.com/FerretDB/FerretDB/actions/runs/6309162567/job/17128566077?pr=3433 This [documentation page](https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#get-a-pull-request) suggests that `merge_commit_sha` can be `null` while GitHub checks the mergeability of the PR in...

@ldez ping!

If someone is using a PAT and is getting the corresponding with the default config on a private repo: ``` Error: RunScorecard: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query:...

Another source of inspiration might be `py_proto_library` from gRPC: https://github.com/grpc/grpc/blob/master/bazel/python_rules.bzl#L160 as `py_proto_library` from rules_python is a recent addition. That said, as someone unfamiliar with the internals of these libraries and...