Skip to content

gsad session#363

Merged
bjoernricks merged 1 commit intomainfrom
gsad-session
Apr 7, 2026
Merged

gsad session#363
bjoernricks merged 1 commit intomainfrom
gsad-session

Conversation

@bjoernricks
Copy link
Copy Markdown
Contributor

What

Use prefix for the gsad session

Why

All gsad code should use the gsad prefix.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.43%. Comparing base (794d94c) to head (8c721d6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #363   +/-   ##
=======================================
  Coverage   94.43%   94.43%           
=======================================
  Files          24       24           
  Lines        3900     3900           
  Branches       80       80           
=======================================
  Hits         3683     3683           
  Misses        179      179           
  Partials       38       38           
Flag Coverage Δ
unittests 94.43% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

All gsad code should use the gsad prefix.
@bjoernricks bjoernricks marked this pull request as ready for review April 7, 2026 07:00
@bjoernricks bjoernricks requested review from a team as code owners April 7, 2026 07:00
@bjoernricks bjoernricks enabled auto-merge (rebase) April 7, 2026 07:11
@bjoernricks bjoernricks merged commit 9b5ecf4 into main Apr 7, 2026
21 checks passed
@bjoernricks bjoernricks deleted the gsad-session branch April 7, 2026 08:24
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