Skip to content

No failed test#4

Draft
peevees wants to merge 3 commits into
masterfrom
no-failed-test
Draft

No failed test#4
peevees wants to merge 3 commits into
masterfrom
no-failed-test

Conversation

@peevees
Copy link
Copy Markdown
Owner

@peevees peevees commented Dec 15, 2020

Description

quick fixes all tests to not fail
copilot:walkthrough

Related Issue

Motivation and Context

to test githubs branch protection and to see github actions that doesn't fail and to see code coverage result

How Has This Been Tested?

it hasn't 😉

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@peevees peevees force-pushed the no-failed-test branch 4 times, most recently from 850b2e4 to c4fec23 Compare March 15, 2022 13:19
@peevees peevees force-pushed the no-failed-test branch 5 times, most recently from a0f20f3 to 43394c5 Compare March 15, 2022 15:12
@peevees peevees mentioned this pull request Mar 15, 2022
@github-actions
Copy link
Copy Markdown

Code Coverage

Package Line Rate Branch Rate Complexity
Summary 100% (0 / 0) 100% (0 / 0) 0

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant