This repository has been archived by the owner on Jan 5, 2024. It is now read-only.
Prepare for retirement #177
Merged
Conversation
This file contains 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
47 tasks
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #177 +/- ##
==========================================
+ Coverage 95.36% 95.37% +0.01%
==========================================
Files 17 17
Lines 798 800 +2
==========================================
+ Hits 761 763 +2
Misses 37 37 ☔ View full report in Codecov by Sentry. |
willGraham01
force-pushed
the
prepare-for-retirement
branch
from
d2b5f1a
to
f96c5ad
Compare
alessandrofelder
approved these changes
Dec 13, 2023
alessandrofelder
approved these changes
Dec 13, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Marks the package for deprecation, as per brainglobe/BrainGlobe#46.
Merging to be followed by a new version release, at
<v1.0.0.Rebase onto
mainrecommended before merging, to catch any additional changes.