[INFRA] Debian cron #3333
Merged
[INFRA] Debian cron #3333
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seqan-actions
added
lint
Member
|
Documentation preview available at https://docs.seqan.de/preview/seqan/seqan3/3333 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3333 +/- ##
=======================================
Coverage 98.11% 98.11%
=======================================
Files 270 270
Lines 11913 11913
Branches 104 104
=======================================
Hits 11688 11688
Misses 225 225 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This builds the Debian package on the main branch.
It's basically an API-Stability check for our package builds.
Errors either mean that something was overlooked when changing code or that the Debian package would need patches. In the latter case, it's nice to see that before an RC is released because there are way fewer commits between cron runs than between a stable release and the first release candidate of the next version.