Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Gen 1180 claimer should validate timetoreachmaxfee #27

Merged
merged 4 commits into from
Mar 1, 2024
Merged

Gen 1180 claimer should validate timetoreachmaxfee #27

merged 4 commits into from
Mar 1, 2024

Conversation

asselstine
Copy link
Contributor

No description provided.

@linear Linear
Copy link

linear bot commented Feb 29, 2024

GEN-1180 Claimer should validate _timeToReachMaxFee

@github-actions GitHub Actions
Copy link

LCOV of commit a544618 during Tests with 100% Coverage #129

Summary coverage rate:
  lines......: 100.0% (76 of 76 lines)
  functions..: 100.0% (15 of 15 functions)
  branches...: no data found

Files changed coverage rate:
                                  |Lines       |Functions  |Branches    
  Filename                        |Rate     Num|Rate    Num|Rate     Num
  ======================================================================
  src/Claimer.sol                 | 100%     45| 100%     9|    -      0

@asselstine asselstine requested a review from trmid March 1, 2024 01:28
@asselstine asselstine merged commit 499bef4 into main Mar 1, 2024
2 checks passed
@asselstine asselstine deleted the gen-1180-claimer-should-validate-_timetoreachmaxfee branch March 1, 2024 01:28
trmid
trmid reviewed Mar 1, 2024
View reviewed changes
Copy link
Member

@trmid trmid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@trmid trmid trmid left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@asselstine @trmid