Audited qiskit.org links #381
Conversation
I intended it to be in scope. But we could create a follow up issue if we want? |
Yeah, like with other API updates I think first and foremost this should be the responsibility of the devs that create the API reference. At least for now as our workload is so high as is. Perhaps we could open issues in the other repos? |
I'm fine with that in general in the future for long-term maintenance. But as the team responsible for the qiskit.org migration, I do think it's appropriate for our team to do. It should be fine if this slips from https://github.com/Qiskit/documentation/milestone/3 to https://github.com/Qiskit/documentation/milestone/5 thanks to redirects. |
| - Experiment with the [migration tutorial.](https://qiskit.org/ecosystem/ibm-provider/tutorials/Migration_Guide_from_qiskit-ibmq-provider.html) | ||
| - Experiment with the [migration tutorial.](./qiskit-runtime) |
There was a problem hiding this comment.
This is a reference to itself
There was a problem hiding this comment.
ah ok, maybe I should just remove this link entirely then, ad that old provider url has been replaced with this page
Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com>
This PR replaces any qiskit.org links with 1XP or github equivalents. Need to wait to merge until I can update the deprecation policy and maintainer guide links after Qiskit/qiskit#11218 merges. This should partially resolve Qiskit#297 , however for the api links we'll need to make updates for those directly in the repos where the API refs live (maybe this is beyond the scope of the original issue?) --------- Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com>
This PR replaces any qiskit.org links with 1XP or github equivalents. Need to wait to merge until I can update the deprecation policy and maintainer guide links after Qiskit/qiskit#11218 merges.
This should partially resolve #297 , however for the api links we'll need to make updates for those directly in the repos where the API refs live (maybe this is beyond the scope of the original issue?)