Olivier Halligon

> Based on your job logs, I don't think you are manually calling buildkite-agent redactor add with env vars. Rather, you're using s3-secrets-hooks which is what is calling it. I...

> It seems reasonable that there is no name check or minimum length check in buildkite-agent redactor add or the Job API - if a customer wants to redact a...

Btw FYI, some more context to our specific use case to explain why we set that `BUILDKITE_AGENT_PIPELINE_UPLOAD_REJECT_SECRETS` env var via `s3-secrets-helper` even if that variable value isn't really a secret...

@DrJosh9000 I took a stab at trying to fix this in https://github.com/buildkite/elastic-ci-stack-s3-secrets-hooks/pull/146 (Bear with me, this is my first time writing Go 😅 but I figured it was a good...

> [!NOTE] > CI failures in this PR that are about Ruby 2.x install failures will be fixed separately once https://github.com/fastlane/fastlane/pull/29734 lands.

I don't have a Linux machine nor project to test this in a real project; has anyone put that PR to the test on a real-world project?

@mokagio I did the same experiment on my end asking my Cursor Composer to generate those docs too, you can see the result in https://github.com/Automattic/a8c-ci-toolkit-buildkite-plugin/pull/160. I left the generated content...

That is indeed good to keep in mind. Though, to be clear, the use of LLM here was never intended to generate (deterministic) documentation. After all, the goal is not...