Fix CI by switching from mysql to postgres requirements install #197
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
Merged
Author
|
As spoken with @Bachibouzouk, I will leave this PR as is. @Bachibouzouk has a solution for the 4 failing tests on |
Bachibouzouk
force-pushed
the
feature/assets-needed-usecase
branch
from
4359b8b to
850b593
Compare
…t have duplicate and or converging requirements
Bachibouzouk
force-pushed
the
fix/ci-workflow
branch
from
c0c1ddf to
cae9d64
Compare
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.
Hi @Bachibouzouk, this is a draft PR it's based on your open PR #183 and tries to solve the Github Workflow issue of not being able to use Postgres for testing.
Please note: This PR wants to be merged into #183. Only after doing so #183 should be merged into
main.I will request for a review if ready. So you don't have to involve yourself for now.