release: staging into main #85
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
* refactor: change the way logging is done, make output directories more explicit (not enforced yet) * style: apply black formatting * ci: change testing output to use 'tee' instead of redirect * test: no subprocess test in ipynb on linux * test: strip metadata by hand from ipynb * refactor: modify logging output formats * refactor: move certain elements out of Model into a BaseModel * refactor(version): move location of version number to avoid circular imports * refactor(test): fix test to match refactor of license and copyright text names
Automatically generated by python-semantic-release
Automatically generated by python-semantic-release * ci: test separate repo for reusable workflows * ci: test separate repo for reusable workflows * ci: test separate repo for reusable workflows * ci: update continuous testing to include semantic release check * chore: modify pyproject release branches specification * ci: update continuous testing to include semantic release check on pyproject.toml modification * ci: add pull request context to quick test * ci: remove automatic prerelease tag from pr builds for time being * ci: update semantic-release workflow for commits to staging --------- Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: David Hart <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: github-actions <[email protected]>
Automatically generated by python-semantic-release
Signed-off-by: David Hart <[email protected]>
* ci: test separate repo for reusable workflows * ci: test separate repo for reusable workflows * ci: test separate repo for reusable workflows * ci: update continuous testing to include semantic release check * chore: modify pyproject release branches specification * ci: update continuous testing to include semantic release check on pyproject.toml modification * ci: add pull request context to quick test * ci: remove automatic prerelease tag from pr builds for time being * ci: update semantic-release workflow for commits to staging * fix: depths as true measured depths not as heights from TD_0 * ci: configure semantic-release on staging branch The semantic-release job will now run on staging and automatically update the version number to the next version and create a new changelog. It will not, however, add a tag or build a release. This may result in a need to synchronize. --------- Signed-off-by: David Hart <[email protected]>
Automatically generated by python-semantic-release
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #85 +/- ##
==========================================
- Coverage 88.05% 87.17% -0.88%
==========================================
Files 9 9
Lines 2001 2051 +50
==========================================
+ Hits 1762 1788 +26
- Misses 239 263 +24
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.