diff --git a/.github/ISSUE_TEMPLATE/NEW_EXPERIMENT.md b/.github/ISSUE_TEMPLATE/NEW_EXPERIMENT.md index 73a2e11e33..cd44168171 100644 --- a/.github/ISSUE_TEMPLATE/NEW_EXPERIMENT.md +++ b/.github/ISSUE_TEMPLATE/NEW_EXPERIMENT.md @@ -85,9 +85,9 @@ different qubits. Verify this also on a real device experiment data is displayed correctly in the results DB webpage - [ ] Add unit testing for the experiment and analysis classes. If needed implement a mock-backend for your experiment Include in your testing running the experiment in the context of `ParallelExperiment` -- [ ] Write API docs for all your API methods. Follow the guideline [here](https://github.com/Qiskit-Extensions/qiskit-experiments/blob/main/CONTRIBUTING.md) -- [ ] Write a user guide for your experiment. Follow the guideline [here](https://github.com/Qiskit-Extensions/qiskit-experiments/blob/main/docs/GUIDELINES.md) -- [ ] Add a new release note. Follow the guideline [here](https://github.com/Qiskit-Extensions/qiskit-experiments/blob/main/CONTRIBUTING.md#adding-a-new-release-note) +- [ ] Write API docs for all your API methods. Follow the guideline [here](https://github.com/Qiskit-Community/qiskit-experiments/blob/main/CONTRIBUTING.md) +- [ ] Write a user guide for your experiment. Follow the guideline [here](https://github.com/Qiskit-Community/qiskit-experiments/blob/main/docs/GUIDELINES.md) +- [ ] Add a new release note. Follow the guideline [here](https://github.com/Qiskit-Community/qiskit-experiments/blob/main/CONTRIBUTING.md#adding-a-new-release-note) - [ ] Ask for a final review for the implementation, documentation and testing - [ ] Celebrate! diff --git a/.github/workflows/cron-staging.yml b/.github/workflows/cron-staging.yml index 0f9c667bc3..4b7a82ea61 100644 --- a/.github/workflows/cron-staging.yml +++ b/.github/workflows/cron-staging.yml @@ -6,7 +6,7 @@ on: jobs: qiskit-main-tests: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' name: tests-python${{ matrix.python-version }}-${{ matrix.os }} runs-on: ${{ matrix.os }} strategy: @@ -46,7 +46,7 @@ jobs: env: TEST_TIMEOUT: 120 docs: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' name: docs runs-on: ubuntu-latest steps: diff --git a/.github/workflows/docs_dev.yml b/.github/workflows/docs_dev.yml index a2f0d03b50..5a9851ebfc 100644 --- a/.github/workflows/docs_dev.yml +++ b/.github/workflows/docs_dev.yml @@ -6,7 +6,7 @@ on: jobs: deploy: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 diff --git a/.github/workflows/docs_release.yml b/.github/workflows/docs_release.yml index 38e517b057..d8680bf56d 100644 --- a/.github/workflows/docs_release.yml +++ b/.github/workflows/docs_release.yml @@ -7,7 +7,7 @@ on: jobs: deploy: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 diff --git a/.github/workflows/docs_stable.yml b/.github/workflows/docs_stable.yml index fa32b8c42c..966e261025 100644 --- a/.github/workflows/docs_stable.yml +++ b/.github/workflows/docs_stable.yml @@ -7,7 +7,7 @@ on: jobs: deploy: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 0e660d004b..63009e687c 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -11,7 +11,7 @@ concurrency: cancel-in-progress: true jobs: tests: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' name: tests-python${{ matrix.python-version }}-${{ matrix.os }} runs-on: ${{ matrix.os }} strategy: @@ -62,7 +62,7 @@ jobs: run: stestr history remove all lint: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' name: lint runs-on: ubuntu-latest steps: @@ -81,7 +81,7 @@ jobs: - name: Run lint run: tox -elint docs: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' name: docs runs-on: ubuntu-latest steps: diff --git a/.github/workflows/neko.yml b/.github/workflows/neko.yml index c4f3736139..d886e8e79f 100644 --- a/.github/workflows/neko.yml +++ b/.github/workflows/neko.yml @@ -8,7 +8,7 @@ concurrency: cancel-in-progress: true jobs: neko: - if: github.repository_owner == 'Qiskit-Extensions' + if: github.repository_owner == 'Qiskit-Community' name: Qiskit Neko Integration Tests runs-on: ubuntu-latest steps: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0a35679c5b..3b174680da 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,7 +38,7 @@ experimentalist community. If there is an experiment you would like to see added, you can propose it by creating a [new experiment proposal -issue](https://github.com/Qiskit-Extensions/qiskit-experiments/issues/new?assignees=&labels=enhancement&template=NEW_EXPERIMENT.md&title=) +issue](https://github.com/Qiskit-Community/qiskit-experiments/issues/new?assignees=&labels=enhancement&template=NEW_EXPERIMENT.md&title=) in GitHub. The issue template will ask you to fill in details about the experiment type, protocol, analysis, and implementation, which will give us the necessary information to decide whether the experiment is feasible to implement and useful to include in our @@ -49,12 +49,12 @@ We use the following labels to help non-maintainers find issues best suited to t interests and experience level: * [good first - issue](https://github.com/Qiskit-Extensions/qiskit-experiments/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) + issue](https://github.com/Qiskit-Community/qiskit-experiments/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) - these issues are typically the simplest available to work on, perfect for newcomers. They should already be fully scoped, with a clear approach outlined in the descriptions. * [help - wanted](https://github.com/Qiskit-Extensions/qiskit-experiments/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) + wanted](https://github.com/Qiskit-Community/qiskit-experiments/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22) - these issues are generally more complex than good first issues. They typically cover work that core maintainers don't currently have capacity to implement and may require more investigation/discussion. These are a great option for experienced contributors @@ -275,7 +275,7 @@ deprecations: Note that we are using subsections within the `features`, `upgrade`, and `fixes` sections to organize the notes by functional area. We strongly encourage you to file your note under the most appropriate category. You can see the current list of categories in -[release_notes/config.yaml](https://github.com/Qiskit-Extensions/qiskit-experiments/blob/main/releasenotes/config.yaml). +[release_notes/config.yaml](https://github.com/Qiskit-Community/qiskit-experiments/blob/main/releasenotes/config.yaml). You can use any restructured text feature in them (code sections, tables, enumerated lists, bulleted list, etc.) to express what is being changed as needed. In general, you @@ -296,7 +296,7 @@ example you would write a release note with a link to issue 12345 as: fixes: - | Fixed a race condition in the function ``foo()``. Refer to - `#12345 ` for more + `#12345 ` for more details. ``` @@ -317,11 +317,11 @@ tagged): At release time, ``reno report`` is used to generate the release notes for the release, and the output will be submitted as a pull request to the documentation repository's [release notes file]( -https://github.com/Qiskit-Extensions/qiskit-experiments/blob/main/docs/release_notes.rst). +https://github.com/Qiskit-Community/qiskit-experiments/blob/main/docs/release_notes.rst). ### Documentation -The [Qiskit Experiments documentation](https://qiskit-extensions.github.io/qiskit-experiments) is +The [Qiskit Experiments documentation](https://qiskit-community.github.io/qiskit-experiments) is rendered from `.rst` files as well as experiment and analysis class docstrings into HTML files. @@ -329,7 +329,7 @@ files. Any change that would affect existing documentation, or a new feature that requires a documentation, should be updated correspondingly. Before updating, review the [existing -documentation](https://qiskit-extensions.github.io/qiskit-experiments) for their style and +documentation](https://qiskit-community.github.io/qiskit-experiments) for their style and content, and read the [documentation guidelines](docs/GUIDELINES.md) for further details. @@ -355,7 +355,7 @@ will remove Sphinx's cache. If you are still having issues, try adding `-r` your e.g. `tox -e docs -r`. `-r` tells Tox to reinstall the dependencies. If you encounter a build error involving `config-inited`, you need to be in the root of the qiskit-experiments git repository then run `git remote add upstream -https://github.com/Qiskit-Extensions/qiskit-experiments` and `git fetch upstream` before building. +https://github.com/Qiskit-Community/qiskit-experiments` and `git fetch upstream` before building. There are a few other build options available: @@ -440,7 +440,7 @@ policy](https://github.com/Qiskit/qiskit/blob/1.0.0rc1/DEPRECATION.md#issuing-de The development cycle for Qiskit Experiments is all handled in the open using project boards in GitHub for project management. We use -[milestones](https://github.com/Qiskit-Extensions/qiskit-experiments/milestones) in GitHub to track +[milestones](https://github.com/Qiskit-Community/qiskit-experiments/milestones) in GitHub to track work for specific releases. Features or other changes that we want to include in a release will be tagged and discussed in GitHub. diff --git a/README.md b/README.md index 1db2dcd42d..70f16dd996 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # Qiskit Experiments -[![License](https://img.shields.io/github/license/Qiskit-Extensions/qiskit-experiments.svg)](https://opensource.org/licenses/Apache-2.0) -[![Release](https://img.shields.io/github/release/Qiskit-Extensions/qiskit-experiments.svg)](https://github.com/Qiskit-Extensions/qiskit-experiments/releases) +[![License](https://img.shields.io/github/license/Qiskit-Community/qiskit-experiments.svg)](https://opensource.org/licenses/Apache-2.0) +[![Release](https://img.shields.io/github/release/Qiskit-Community/qiskit-experiments.svg)](https://github.com/Qiskit-Community/qiskit-experiments/releases) ![Python](https://img.shields.io/pypi/pyversions/qiskit-experiments.svg) [![DOI](https://joss.theoj.org/papers/10.21105/joss.05329/status.svg)](https://doi.org/10.21105/joss.05329) @@ -9,9 +9,9 @@ and analyzing experiments on noisy quantum computers using Qiskit. To learn more about the package, you can see the -[most up-to-date documentation](https://qiskit-extensions.github.io/qiskit-experiments/dev) +[most up-to-date documentation](https://qiskit-community.github.io/qiskit-experiments/dev) corresponding to the main branch of this repository or the -[documentation for the latest stable release](https://qiskit-extensions.github.io/qiskit-experiments). +[documentation for the latest stable release](https://qiskit-community.github.io/qiskit-experiments). ## Contribution Guidelines @@ -20,7 +20,7 @@ If you'd like to contribute to Qiskit Experiments, please take a look at our [code of conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. -We use [GitHub issues](https://github.com/Qiskit-Extensions/qiskit-experiments/issues) for +We use [GitHub issues](https://github.com/Qiskit-Community/qiskit-experiments/issues) for tracking requests and bugs. Please [join the Qiskit Slack community](https://qisk.it/join-slack) and use the [#experiments](https://qiskit.slack.com/archives/CGZDF48EN) channel for discussion and @@ -30,7 +30,7 @@ For questions that are more suited for a forum we use the Qiskit tag in ## Authors and Citation -Qiskit Experiments is the work of [many people](https://github.com/Qiskit-Extensions/qiskit-experiments/graphs/contributors) who contribute +Qiskit Experiments is the work of [many people](https://github.com/Qiskit-Community/qiskit-experiments/graphs/contributors) who contribute to the project at different levels. If you use Qiskit Experiments, please cite our [paper](https://doi.org/10.21105/joss.05329) as per the included [citation file](CITATION.cff). diff --git a/docs/GUIDELINES.md b/docs/GUIDELINES.md index 282e013646..293539d6ee 100644 --- a/docs/GUIDELINES.md +++ b/docs/GUIDELINES.md @@ -162,7 +162,7 @@ example and example outputs by printing relevant analysis results and plot figur Required and common parameters, such as experiment and analysis options, should be covered. -See the [Randomized Benchmarking](https://qiskit-extensions.github.io/qiskit-experiments/manuals/verification/randomized_benchmarking.html) +See the [Randomized Benchmarking](https://qiskit-community.github.io/qiskit-experiments/manuals/verification/randomized_benchmarking.html) guide and its [source code](manuals/verification/randomized_benchmarking.rst) for an example. Here is a simple template for a manual: @@ -276,7 +276,7 @@ There are several predefined sections for the class docstring. For referring to the website, - .. ref_website:: Qiskit Experiment GitHub, https://github.com/Qiskit-Extensions/qiskit-experiments + .. ref_website:: Qiskit Experiment GitHub, https://github.com/Qiskit-Community/qiskit-experiments you can use the above macro, where you can provide a string for the hyperlink and the destination location separated by single comma. @@ -380,9 +380,9 @@ header should be named `Analysis Options` to be parsed correctly. After you complete documentation of your classes, you must add documentation to the toctree so that it can be rendered as the API documentation. In Qiskit Experiments, we have a separate tables of contents for each experiment module (e.g. [characterization -experiments](https://qiskit-extensions.github.io/qiskit-experiments/apidocs/mod_characterization.html)) +experiments](https://qiskit-community.github.io/qiskit-experiments/apidocs/mod_characterization.html)) and for the [entire -library](https://qiskit-extensions.github.io/qiskit-experiments/apidocs/library.html). Thus we +library](https://qiskit-community.github.io/qiskit-experiments/apidocs/library.html). Thus we should add document to the tree of a particular module and then reference it to the entire module. diff --git a/docs/_ext/autoref.py b/docs/_ext/autoref.py index 15606221fe..b4f820a1c6 100644 --- a/docs/_ext/autoref.py +++ b/docs/_ext/autoref.py @@ -27,7 +27,7 @@ class WebSite(Directive): .. code-block:: - .. ref_website:: qiskit-experiments, https://github.com/Qiskit-Extensions/qiskit-experiments + .. ref_website:: qiskit-experiments, https://github.com/Qiskit-Community/qiskit-experiments """ diff --git a/docs/conf.py b/docs/conf.py index 27d4ba580d..151ffb9e72 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -165,7 +165,7 @@ "uncertainties": ("https://pythonhosted.org/uncertainties", None), "pandas": ("http://pandas.pydata.org/docs/", None), "qiskit_aer": ("https://qiskit.github.io/qiskit-aer/", None), - "qiskit_dynamics": ("https://qiskit-extensions.github.io/qiskit-dynamics/", None), + "qiskit_dynamics": ("https://qiskit-community.github.io/qiskit-dynamics/", None), "qiskit_ibm_runtime": ("https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/", None), } @@ -176,7 +176,7 @@ rst_prolog = """ .. note:: This is the documentation for the current state of the `development branch - `_ + `_ of Qiskit Experiments. The documentation or APIs here can change prior to being released. """ diff --git a/docs/howtos/index.rst b/docs/howtos/index.rst index 1716563c80..8759b44ab1 100644 --- a/docs/howtos/index.rst +++ b/docs/howtos/index.rst @@ -15,7 +15,7 @@ familiarize with :ref:`the basics ` of the package before using these gu | If there are guides on solving specific problems that you'd like to see added, please -`file an issue on GitHub `_. +`file an issue on GitHub `_. | diff --git a/docs/index.rst b/docs/index.rst index 77020e517c..707ec39b50 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -102,8 +102,8 @@ We've divided up the documentation into four sections with different purposes: manuals/index apidocs/index release_notes - GitHub - Development Branch Docs + GitHub + Development Branch Docs | diff --git a/docs/release_notes.rst b/docs/release_notes.rst index 87575aad81..63e04cdb38 100644 --- a/docs/release_notes.rst +++ b/docs/release_notes.rst @@ -30,7 +30,7 @@ Bug Fixes :mod:`qiskit_dynamics` version 0.5.0. The updates accounted for changes in the expected arguments to Dynamics API's and did not change behavior. See `#1427 - `__. + `__. .. releasenotes/notes/figure-names-inconsistency-afca1ac8e00fabac.yaml @ b'32813b86b04b956bb7b1334759a79af6ce9068df' @@ -38,7 +38,7 @@ Bug Fixes with ``replace_results=True`` does not result in the ``figure_names`` property having incorrect data (both old and new figure names if the names changed). See `#1430 - `__. + `__. .. releasenotes/notes/figure-names-inconsistency-afca1ac8e00fabac.yaml @ b'32813b86b04b956bb7b1334759a79af6ce9068df' @@ -46,7 +46,7 @@ Bug Fixes argument to the ``run()`` method. Previously, this argument was ignored and ``figure_names`` could only be set as an analysis option prior to calling ``run()``. See `#1430 - `__. + `__. .. releasenotes/notes/mock-iq-backend-without-qiskit-runtime-20d2bf9edb48312d.yaml @ b'2045689df74b74a94f1f5e5a8d4598354c4e5385' @@ -58,7 +58,7 @@ Bug Fixes .. releasenotes/notes/remove_backendv2-b608a2f380698710.yaml @ b'5c6f4b2c8226bca2276c5eecfab5193748a8e524' - Removed a ``FakeBackendV2`` import path which would have been incompatible with Qiskit 1.1 and above. See - `#1420 `_. + `#1420 `_. .. _Release Notes_0.6.0: @@ -155,7 +155,7 @@ Experiment Class Features - A new method :meth:`.BaseExperiment.job_info` has been added that will output the number of jobs the experiment is expected to be split into based on the provided backend. Refer to issue - `#1247 `_ + `#1247 `_ for more details. .. releasenotes/notes/0.6/setter-methods-for-experiment-099074e59faffb49.yaml @ b'e8531c4f6af9432827bc28c772c5a179737f0c3c' @@ -338,7 +338,7 @@ Visualization Features - An :meth:`~.BaseDrawer.hline` method was added to :class:`.BaseDrawer` for generating horizontal lines. See `#1348 - `__. + `__. .. releasenotes/notes/0.6/qvplotter-04efe280aaa9d555.yaml @ b'e8531c4f6af9432827bc28c772c5a179737f0c3c' @@ -350,7 +350,7 @@ Visualization Features as in previous releases, but now it is easier to customize the figure by setting options on the plotter object. See `#1348 - `__. + `__. .. releasenotes/notes/0.6/scale_options-745ee6f8e560043f.yaml @ b'e8531c4f6af9432827bc28c772c5a179737f0c3c' @@ -369,7 +369,7 @@ Known Issues - Copied :class:`.ExperimentData` objects don't save their analysis results to the cloud service. See `#1396 - `_. + `_. .. _Release Notes_0.6.0_Upgrade Notes: @@ -606,7 +606,7 @@ Experiment Library Fixes Previously, it could only be run through the :class:`.HalfAngleCal` subclass in combination with a :class:`.Calibrations` instance containing a custom calibration for the ``y`` gate. - Fixes issue `#1233 `_. + Fixes issue `#1233 `_. .. releasenotes/notes/0.6/plugable-rb-clifford-synthesis-0e66c62fa3088fba.yaml @ b'e8531c4f6af9432827bc28c772c5a179737f0c3c' @@ -614,7 +614,7 @@ Experiment Library Fixes sampled Cliffords may be changed during their circuits synthesis (in the worst case, the resulting circuits may use qubits not in ``physical_qubits``). See issue - `#1279 `_ + `#1279 `_ for additional details. .. releasenotes/notes/0.6/rabi-and-qv-bugfix-34636baee6651af1.yaml @ b'e8531c4f6af9432827bc28c772c5a179737f0c3c' @@ -648,7 +648,7 @@ Experiment Data Fixes deserialized using Python's ``pickle`` module, but deserialized objects were not completely restored and an exception would be raised when doing some operations like running analysis on the restored object. See `#1326 - `__. + `__. .. releasenotes/notes/0.6/experiment_data_fixes-f69c3569a8ba1342.yaml @ b'e8531c4f6af9432827bc28c772c5a179737f0c3c' @@ -815,7 +815,7 @@ Bug Fixes ``qiskit-aer`` 0.13.0. Version 0.13.0 of ``qiskit-aer`` changed the default :class:`qiskit_aer.AerSimulator` to have such a :class:`qiskit.transpiler.Target` without specific coupled pairs. - See `#1292 `__. + See `#1292 `__. .. _Release Notes_0.5.4_Other Notes: @@ -829,7 +829,7 @@ Other Notes Since qubits are usually reset between circuits, this change should have no impact on tomography experiments, but it should allow backends that do not provide a reset instruction to run tomography experiments. See `#1250 - `__. + `__. .. _Release Notes_0.5.3: diff --git a/docs/tutorials/getting_started.rst b/docs/tutorials/getting_started.rst index 5c5092b0cd..72062fde4a 100644 --- a/docs/tutorials/getting_started.rst +++ b/docs/tutorials/getting_started.rst @@ -28,14 +28,14 @@ install the latest main branch: .. code-block:: - python -m pip install git+https://github.com/Qiskit-Extensions/qiskit-experiments.git + python -m pip install git+https://github.com/Qiskit-Community/qiskit-experiments.git If you want to develop the package, you can install Qiskit Experiments from source by cloning the repository: .. code-block:: - git clone https://github.com/Qiskit-Extensions/qiskit-experiments.git + git clone https://github.com/Qiskit-Community/qiskit-experiments.git python -m pip install -e "qiskit-experiments[extras]" The ``-e`` option will keep your installed package up to date as you make or pull new diff --git a/releasenotes/notes/0.7/fix-ecr-epg-59c8db98494966b0.yaml b/releasenotes/notes/0.7/fix-ecr-epg-59c8db98494966b0.yaml index ce78428727..b370d59978 100644 --- a/releasenotes/notes/0.7/fix-ecr-epg-59c8db98494966b0.yaml +++ b/releasenotes/notes/0.7/fix-ecr-epg-59c8db98494966b0.yaml @@ -6,5 +6,5 @@ fixes: as a 2-qubit basis gate (e.g. IBM Eagle processors). See `#1419 - `_. + `_. for the details of the bug. diff --git a/setup.py b/setup.py index fdb4b0529e..08d71a949e 100644 --- a/setup.py +++ b/setup.py @@ -38,7 +38,7 @@ description="Software for developing quantum computing programs", long_description=README, long_description_content_type="text/markdown", - url="https://github.com/Qiskit-Extensions/qiskit-experiments", + url="https://github.com/Qiskit-Community/qiskit-experiments", author="Qiskit Development Team", author_email="qiskit@us.ibm.com", license="Apache 2.0", @@ -65,9 +65,9 @@ include_package_data=True, python_requires=">=3.8", project_urls={ - "Bug Tracker": "https://github.com/Qiskit-Extensions/qiskit-experiments/issues", - "Documentation": "https://qiskit-extensions.github.io/qiskit-experiments", - "Source Code": "https://github.com/Qiskit-Extensions/qiskit-experiments", + "Bug Tracker": "https://github.com/Qiskit-Community/qiskit-experiments/issues", + "Documentation": "https://qiskit-community.github.io/qiskit-experiments", + "Source Code": "https://github.com/Qiskit-Community/qiskit-experiments", }, zip_safe=False, entry_points={ diff --git a/tox.ini b/tox.ini index fbb6447084..a00cc60f99 100644 --- a/tox.ini +++ b/tox.ini @@ -54,7 +54,7 @@ basepython = python3 allowlist_externals = git commands = black --check {posargs} qiskit_experiments test tools setup.py - -git fetch -q https://github.com/Qiskit-Extensions/qiskit-experiments :lint_incr_latest + -git fetch -q https://github.com/Qiskit-Community/qiskit-experiments :lint_incr_latest python {toxinidir}/tools/pylint_incr.py -rn {posargs} -sn --paths :/qiskit_experiments/*.py :/test/*.py :/tools/*.py python {toxinidir}/tools/verify_headers.py qiskit_experiments test tools