OpenZeppelin / OpenZeppelin/compact-tools
feat: add PR lifecycle workflow
Open
Nobody has claimed this yet.
- #69 by @0xisk — closed without merging
enhancement
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 5
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 31
Description
🧐 Motivation
📝 Details
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 provides no files, tests, entry points, or lifecycle requirements to start from. First inspect the repository's existing workflow configuration and clarify which pull-request states and transitions must be handled; done should be defined by an agreed workflow behavior and tests or checks for each required transition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100