protofire
/
safe-modules
100%
master: 100%
master: 100%
|
Repo Added
|
Build
5
Last
|
Files
3
|
Badge
Embed ▾
README BADGES
|
LAST BUILD ON BRANCH add_taiko_networks
coverage: 100.0%. Remained the same
push
github
22 of 22 branches covered (100.0%)
Branch coverage included in aggregate %.
29 of 29 relevant lines covered (100.0%)
19.83 hits per line
Relevant lines Covered
29
RELEVANT LINES
29
COVERED LINES
19.83
HITS PER LINE
Source Files on master
Recent builds
| Builds | Branch | Commit | Type | Ran | Committer | Via | Coverage |
|---|---|---|---|---|---|---|---|
| 11663530023 | add_taiko_networks | feat: add taiko networks | push |  ajimeno04 |
github |
100.0 |
|
| 11607526674 | add_zilliqa | feat: add zilliqa network to allowances | push | ajimeno04 |
github |
100.0 |
|
| 8151594543 | protofire | feat: update patch for safe singleton factory | push |  ElvisKrop |
github |
100.0 |
|
| 7023290046 | protofire | feat: add custom network configuration | push | ElvisKrop |
github |
100.0 |
|
| 7005043327 | master | Internal Function Naming Convention (#171) In preparing for the v0.1.1 audit, I noticed we (i.e. me) forgot to follow internal function naming convention for `_getOperationData`. This PR fixes that (already fixed in the `v0.1` branch) and moves... | push |  web-flow |
github |
100.0 |
 |
Badge your Repo: safe-modulesWe detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message. |
|
Embed ▾
Refresh
README BADGES
|