Setup BCR release automation
Open
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 22
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
I didn't set this up initially because it seems like we either need a fork of the BCR on this repo, or a PAT
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First determine how this repository is expected to publish to BCR and whether the intended approach is a fork or a PAT; done means release automation is configured and its required access method is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100