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.
Follow-up to PR #61.
The previous PR had some issues:
git whatchanged
failed becauseactions/checkout@v2
only checks out the latest commit by default. Fixed by settingfetch-depth
to0
in order to check out the full history. (In the unforeseeable future, there might be afetch-refs
option to optimize this, see revise adr to support fetch-refs actions/checkout#155)--overwrite-output
option that is used intest_changes.sh
database_pipeline.py
created a session during load time, which complicates things when we do not actually need the DatabasePipeline. refactored session creation into theget_session()
method to be more flexible here.@k-nut : Please take a closer look at the session management (6791182). I do have the feeling that our session handling could be improved (i, e. using a fewer number of opened sessions overall).
test_changes.py
(!) so that its output is helpful in more cases