Add verification of initialization data in the database #21
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
raczu
added
scope: backend
|
The new workflow is not passing due to existing error described in #16. |
wzarek
added
the
status: ready for review
wzarek
added
type: feature
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.
Description
Added a workflow that, which at each pull request verifies the correctness of sql files used to initalize the database and development data. Additionally, it fixes wrong path in artifact upload for the unit tests workflow.
Motivation
Workflow was added to avoid potential issues resulting from the mistakes/errors occurring in sql files.
Related issue and/or ticket
RSN-50
This PR closes #20