bazelbuild / bazelbuild/bazelisk
Allow Bazelisk to be more general
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 424
- PR merge metrics
- No merged PRs in 30d
Description
Was hoping to allow bazelisk to install a bazel binary from a repo that is not a fork of bazel but a different repo and doesn't have the same name (bazel).
This issue is just asking if you would be open to prs with this goal.
The defaults would stay the same and there would be no changes for other users who did not want these features.
Thank you for considering :)
Contributor guide
Research direction
The issue names no files, tests, or entry points. First clarify the configuration and repository behavior needed for installing a Bazel binary from a differently named, non-fork repository; done means the new option works while existing defaults and users remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100