-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Abha linking process #7000
Conversation
✅ Deploy Preview for care-egov-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Passing run #1894 ↗︎
Details:
Review all test suite changes for PR #7000 ↗︎ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@nihal467 this is an existing issue, will create a new issue to handle this (it is a backend issue). It is caused because of trying to link the same Abha number multiple times |
LGTM |
1 similar comment
LGTM |
@khavinshankar We truly appreciate your efforts. Thank you for taking the time to contribute; this is a very valuable contribution to us 🥇. We always welcome your contribution 🙂, so feel free to contribute to anything anytime, and never lose that spirit of innovation 🙌. |
Resolves #6999
Todo:
Have a draft for the Abha linking process, the user should be able to continue from where they left off before(will be handled in a new pr)Already have an Abha number
should be there till the end of registration