[credentialhelper] Update flag doc to point to more convenient usage instructions #21382
Conversation
…instructions Arguably, we should have a dedicated page for this on `bazel.build`, but until we have that, this post seems like a better source for users than the original design doc.
github-actions
bot
added
the
awaiting-review
|
@bazel-io fork 7.1.0 |
tjgq
added
awaiting-PR-merge
There was a problem hiding this comment.
While the blog post clarifies how to use a credential helper, it doesn't describe how to write one. But I agree that the proposal isn't the right artifact to link to. How about we also link to https://github.com/EngFlow/credential-helper-spec/blob/main/spec.md?
tjgq
added
awaiting-user-response
SG, done. PTAL |
tjgq
added
awaiting-PR-merge
github-actions
bot
removed
the
awaiting-PR-merge
…instructions Arguably, we should have a dedicated page for this on `bazel.build`, but until we have that, this post seems like a better source for users than the original design doc. Closes bazelbuild#21382. PiperOrigin-RevId: 608747673 Change-Id: Iaca0dc8364a6d622f685bdd53eea54068c4ea94c
…t usage instructions (#21441) Arguably, we should have a dedicated page for this on `bazel.build`, but until we have that, this post seems like a better source for users than the original design doc. Closes #21382. Commit f1b02a2 PiperOrigin-RevId: 608747673 Change-Id: Iaca0dc8364a6d622f685bdd53eea54068c4ea94c Co-authored-by: Yannic <yannic@engflow.com>
|
The changes in this PR have been included in Bazel 7.1.0 RC1. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc. |
Arguably, we should have a dedicated page for this on
bazel.build, but until we have that, this post seems like a better source for users than the original design doc.