Jan-Otto Kröpke

I can confirm, that there is no node with .merge-message https://github.com/refined-github/refined-github/blob/d9ea19838067ede2893c25935cb19ff19edd85e9/source/features/update-pr-from-base-branch.tsx#L98 cross-repo PRs (at least, if I do not have the merge permission on upstream) Own Repo ![2024-06-22 18_50_26-Suppression by...

> "can the current user **update** the PR?" I guess, if the current user is the author would be a sufficient condition?

Maybe this indicator (checkbox -> Allow edits) on right side could be treat as indicator  It may not hits > However there are cases where a repo collaborator can...

How I can test PRs?

> You'd have to check out the PR locally, build the extension Is there an reason, why one of the PR actions not building and upload the crx as artifact?...

While transition to slog, I can recommend the https://github.com/go-simpler/sloglint which is available via golangci-lint.

I have Azure experience, you can alway ping me in that context. Same for STACKIT

@beorn7 I created https://github.com/prometheus/prometheus/pull/16460 for Azure maintainer. For STACKIT, I added myself to MAINTAINER as part of #16401

tbh. it's not easy to debug from my side, but I feel one thing a bit strange: > But its not getting deployed, saying the fields referenced through the encrypted...

If ``` helm: valueFiles: - values.yaml - accessToken.enc.yaml ``` returns the same error, then the keys `accessToken.enc.yaml` are wrong. The file should contain `splunkObservability.realm` or `splunkPlatform.endpoint`.