OriginProtocol / OriginProtocol/origin-dollar
Github contract code vs client code PR template
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 152
- Forks
- 115
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 17
Description
Currently we are using a singular PR template. Whenever there is a contract code change we need to be mindful and also copy the security checklist to the PR description.
Would be cool if we were to develop a bot that would periodically check for Pull requests and auto-edit the description and append the security checklist to it.
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 pull_request_template.md and the linked Contract-Code-Review-Example.md security checklist. Determine how contract-code pull requests should be distinguished from client-code changes and how the checklist should be appended. Done means the bot periodically updates applicable pull request descriptions without affecting other pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, solidity
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100