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.

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

GH-22 prepare for v0.0.2 #23

Merged
merged 1 commit into from
Jan 11, 2025
Merged

GH-22 prepare for v0.0.2 #23

merged 1 commit into from
Jan 11, 2025

Conversation

akefirad
Copy link
Owner

No description provided.

@akefirad akefirad force-pushed the G-22-release-v0.0.2 branch from 41e420d to 4dddb63 Compare January 11, 2025 13:45
@codecov-commenter
Copy link

codecov-commenter commented Jan 11, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.11%. Comparing base (1971aa8) to head (4dddb63).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #23   +/-   ##
=======================================
  Coverage   91.11%   91.11%           
=======================================
  Files           2        2           
  Lines          45       45           
  Branches       16       16           
=======================================
  Hits           41       41           
  Partials        4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@akefirad akefirad changed the title GH-22 release v0.0.2 GH-22 prepare for v0.0.2 Jan 11, 2025
@akefirad akefirad merged commit 561cf91 into main Jan 11, 2025
4 checks passed
@akefirad akefirad deleted the G-22-release-v0.0.2 branch January 11, 2025 13:51
Copy link

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true
Contact Qodana team

Contact us at [email protected]

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.

2 participants