-
Notifications
You must be signed in to change notification settings - Fork 28
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
OID4VCI plugin - Fix delete exchange-supported records #460
OID4VCI plugin - Fix delete exchange-supported records #460
Conversation
You'll need to sign your commits. Then we can merge this. |
I, timbl-ont <tim.bloomfield@ontario.ca>, hereby add my Signed-off-by to this commit: c338c50 Signed-off-by: timbl-ont <tim.bloomfield@ontario.ca>
@jamshale DCO has been added. |
The DCO check is still broken. There's info here on how to repair it. https://github.com/hyperledger/aries-acapy-plugins/pull/460/checks?check_run_id=25285335698. You can do the rebase method if you want. I think it's the simplest. |
I, timbl-ont <tim.bloomfield@ontario.ca>, hereby add my Signed-off-by to this commit: c338c50 Signed-off-by: timbl-ont <tim.bloomfield@ontario.ca>
I, timbl-ont <tim.bloomfield@ontario.ca>, hereby add my Signed-off-by to this commit: c338c50 Signed-off-by: timbl-ont <tim.bloomfield@ontario.ca>
I, Tim Bloomfield <tim.bloomfield@ontario.ca>, hereby add my Signed-off-by to this commit: 6695030 Signed-off-by: Tim Bloomfield <tim.bloomfield@ontario.ca>
I, Tim Bloomfield <tim.bloomfield@gmail.com>, hereby add my Signed-off-by to this commit: 212c7b3 Signed-off-by: Tim Bloomfield <tim.bloomfield@gmail.com>
@jamshale thanks for the feedback. It is fixed now. I am switching between two github accounts and did not realize my DCO remediation PR was with a different github config from the initial PR. Anyway, fixed now after signing off on all the authors. |
Dang! there's just a linting issue now at This ones a bit annoying but it's the same in aca-py. |
Signed-off-by: timbl-ont <tim.bloomfield@ontario.ca>
Quick fix on ./oid4vci/exchange-supported/records delete. There is a typo that duplicates the "credential supported identifier" as a parameter causing deletes to fail.
FYI @dbluhm