bazel-contrib / bazel-contrib/multitool
update command: produce concise summary of change
Open
- Dominant language
- Rust
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When automating renovate/dependabot-style freshness PRs, they end up in the changelog of whatever project uses multitool and that makes it hard to parse.
For example https://github.com/aspect-build/rules_lint/pull/343 will end up with entries like the two "Changes from pull-request action"
Perhaps if the `update` command produces a short description, those automation tools can wire it up to the PR title.
Contributor guide
Assessment
This issue has not been assessed yet.