commit | 75f51c5f338d61bbdf7a26c5f624e19bd54419f7 | [log] [tgz] |
---|---|---|
author | Greg Magolan <greg@aspect.dev> | Tue Aug 20 09:44:15 2024 -0400 |
committer | Greg Magolan <greg@aspect.dev> | Tue Aug 20 14:39:22 2024 -0400 |
tree | c4c969a545143e1db89e31ccbfeeef27b7d97c51 | |
parent | cccf5ac1b8487e02d6270d5fd263123c56c9afc1 [diff] |
chore: enable go, shell, yaml formatters and bazel run //:format
Base Starlark libraries and basic Bazel rules which are useful for constructing rulesets and BUILD files.
This module depends on bazel-skylib. In theory all these utilities could be upstreamed to bazel-skylib, but the declared scope of that project is narrow and it‘s very difficult to get anyone’s attention to review PRs there.
bazel-lib is just a part of what Aspect provides:
Installation instructions are included on each release: https://github.com/aspect-build/bazel-lib/releases
To use a commit rather than a release, you can point at any SHA of the repo.
For example to use commit abc123
:
url = "https://github.com/aspect-build/bazel-lib/releases/download/v0.1.0/bazel-lib-v0.1.0.tar.gz"
with a GitHub-provided source archive like url = "https://github.com/aspect-build/bazel-lib/archive/abc123.tar.gz"
strip_prefix = "bazel-lib-0.1.0"
with strip_prefix = "bazel-lib-abc123"
sha256
. The easiest way to do this is to comment out the line, then Bazel will print a message with the correct value.Note that GitHub source archives don't have a strong guarantee on the sha256 stability, see https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes