You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2024. It is now read-only.
In our readme we link to the Qiskit.org homepage which now redirects to https://www.ibm.com/quantum/qiskit, which is not maintained in this repository. Similarly, we link to the Qiskit documentation page.
What is the expected behavior?
Whilst we could and probably should still link to those pages, we probably shouldn't mix the links to pages that are maintained in this repository and other Qiskit pages.
For that, it's probably the easiest to avoid linking in the title of the README and remove the "links navbar" from the top of the README as well. Then, we should have a section with links to "other Qiskit resources / pages" and a link to the entry point of the pages maintained here, which is now https://qiskit.org/advocates.
Screenshots
No response
Device
No response
OS
No response
Browser
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Steps to reproduce the problem
What is the current behavior?
In our readme we link to the Qiskit.org homepage which now redirects to https://www.ibm.com/quantum/qiskit, which is not maintained in this repository. Similarly, we link to the Qiskit documentation page.
What is the expected behavior?
Whilst we could and probably should still link to those pages, we probably shouldn't mix the links to pages that are maintained in this repository and other Qiskit pages.
For that, it's probably the easiest to avoid linking in the title of the README and remove the "links navbar" from the top of the README as well. Then, we should have a section with links to "other Qiskit resources / pages" and a link to the entry point of the pages maintained here, which is now https://qiskit.org/advocates.
Screenshots
No response
Device
No response
OS
No response
Browser
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: