-
Notifications
You must be signed in to change notification settings - Fork 19
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
Update Vocalink data sets to v640 valid as of 12/10/2020 #23
Update Vocalink data sets to v640 valid as of 12/10/2020 #23
Conversation
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.
Hi,
Can you please follow this example? In order to correctly update this module you need to do 3 things:
- Update the data file, which you have already done;
- Update the loadValacdos function;
- Update the docs folder with the correspondent version;
Hi,
As suggested, I have
1. Updated the loadValacdos function;
2. Updated the docs folder with the correspondent version;
Could you please check.
Thanks
Solanki
From: Francisco Cardoso <[email protected]>
Date: Tuesday, 24 November 2020 at 18:58
To: uphold/uk-modulus-checking <[email protected]>
Cc: Solanki Das <[email protected]>, Author <[email protected]>
Subject: Re: [uphold/uk-modulus-checking] Update Vocalink data sets to v640 valid as of 12/10/2020 (#23)
@franciscocardoso requested changes on this pull request.
Hi,
Can you please follow this example<https://github.com/uphold/uk-modulus-checking/pull/16/files>? In order to correctly update this module you need to do 3 things:
1. Update the data file, which you have already done;
2. Update the loadValacdos function;
3. Update the docs folder with the correspondent version;
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#23 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZXDKPKZZ5DAGDL2RELRULSRP65DANCNFSM4T7KOXLA>.
|
Hi,
I have replaced the new file with the old version and squash the commits into one. Please find the attached screenshot of the log.
Thanks
Solanki
From: Francisco Cardoso <[email protected]>
Date: Thursday, 26 November 2020 at 17:26
To: uphold/uk-modulus-checking <[email protected]>
Cc: Solanki Das <[email protected]>, Author <[email protected]>
Subject: Re: [uphold/uk-modulus-checking] Update Vocalink data sets to v640 valid as of 12/10/2020 (#23)
You are removing the pdf file. Please replace it with the new one<https://www.vocalink.com/media/4749/vocalink-validating-account-numbers-v640.pdf> instead.
Also, please don't forget to squash the commits into one. If you are not aware how to do it you can read this<https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#23 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZXDKLF7ONV62EPI4FJZ5DSR2FVPANCNFSM4T7KOXLA>.
|
Hi,
I have already made the changes requested by you. Could you please review and let me know whether any other changes are required.
Regards
Solanki.
From: Solanki Das <[email protected]>
Date: Monday, 30 November 2020 at 15:53
To: uphold/uk-modulus-checking <[email protected]>
Subject: Re: [uphold/uk-modulus-checking] Update Vocalink data sets to v640 valid as of 12/10/2020 (#23)
Hi,
I have replaced the new file with the old version and squash the commits into one. Please find the attached screenshot of the log.
Thanks
Solanki
From: Francisco Cardoso <[email protected]>
Date: Thursday, 26 November 2020 at 17:26
To: uphold/uk-modulus-checking <[email protected]>
Cc: Solanki Das <[email protected]>, Author <[email protected]>
Subject: Re: [uphold/uk-modulus-checking] Update Vocalink data sets to v640 valid as of 12/10/2020 (#23)
You are removing the pdf file. Please replace it with the new one<https://www.vocalink.com/media/4749/vocalink-validating-account-numbers-v640.pdf> instead.
Also, please don't forget to squash the commits into one. If you are not aware how to do it you can read this<https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#23 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARZXDKLF7ONV62EPI4FJZ5DSR2FVPANCNFSM4T7KOXLA>.
|
58bf630
to
b7a768c
Compare
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.
Hi @solanki-das
I took the liberty of squashing the commits.
Thanks for your contribution and effort to keep this module up to date.
No description provided.