OpenZeppelin / OpenZeppelin/openzeppelin-contracts
Consider using eth-gas-reporter's CI integration through codechecks
Open
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 27.2k
- Forks
- 12.4k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 33
Description
We currently track gas cost changes using an in-house github action. We may consider using this instead:
https://github.com/cgewecke/eth-gas-reporter/blob/master/docs/codechecks.md
Contributor guide
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 the linked eth-gas-reporter Codechecks documentation and locating the repository's current in-house GitHub Action for tracking gas cost changes. Compare the existing integration with the proposed approach; the work is done when the project has a decided, documented path for whether and how to use Codechecks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, solidity
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100