@nejcr is attempting to deploy a commit to the KeepHQ Team on Vercel.

A member of the Team first needs to authorize it.

All committers have signed the CLA.

Not sure if I'm right but it might conflict with: #1488 which is about to get merged.

Not sure if I'm right but it might conflict with: #1488 which is about to get merged.

I can wait, looking at it, it would be easier for me if I resolved conflicts afterwards

💵 To receive payouts, sign up on Algora, link your Github account and connect with Stripe.

@nejcr I think your changes are conflicting with my changes. please resolve them. post-resolution can you also share the final changes with me? If needed any clarification on new changes please do reach out to me.

@talboren I have resolved the conflicts with the main branch.

@rajeshj11 I incorporated some of your validator changes as they were necessary for proper functionality. The code should now be free of conflicts. Additionally, I simplified the nested ternary logic for better readability.

Great PR from my point of view, thank you for the contribution! Waiting for tests :) Btw, alembic -c keep/alembic.ini history may help you to fight double-headed migrations (may be the reason E2E test are blocked).

Thank you, @Matvey-Kuk.

I have rebased the changes from the main branch to keep this PR up to date.

Please let me know if anything else is needed. (Note: There were some database setup issues with the tests running on GitHub Actions.)

@nejcr I see the tests are still failing, please let me know if you are planning to fix them

@Matvey-Kuk I believe I’ve fixed it now. The tests passed locally, but I missed the final test run result. My mistake! It seems the unused import wasn’t detected locally. Let me know if there are any more issues.

Great work, thank you!

The latest updates on your projects. Learn more about Vercel for Git ↗︎

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

@Matvey-Kuk @talboren another migration got into main before aproved workflows were triggered.
I've had to resolve another double headed migration.

@Matvey-Kuk looks like something changed so now the pr tests are red.
I have added a possible fix(passes on 1739 branch).

Thank you!