auto-generate protobufs on push
Open
Nobody has claimed this yet.
type: discussion
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
otherwise we'll forget to run build.sh after each change
if committing generated code is not easy, at least error when build should have been run but wasnt
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
Start by reading build.sh and the repository's push-related build configuration, if present, to understand how protobuf generation currently runs. Done means pushes reliably regenerate the protobuf output or report that build.sh was required, with the stale-generated-code case covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100