🚚 Adapt after move to MQT organization (#385)

This PR introduces changes to the package look and feel and prepares the
repository for moving into the [MQT
organization](https://github.com/munich-quantum-toolkit).

---------

Co-authored-by: flowerthrower <flowerthrower@users.noreply.github.com>

Author: flowerthrower

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -8,9 +8,9 @@ body:
         **Thank you for wanting to report a bug for this project!**
 
         ⚠
-        Verify first that your issue is not [already reported on GitHub](https://github.com/cda-tum/mqt-predictor/search?q=is%3Aissue&type=issues).
+        Verify first that your issue is not [already reported on GitHub](https://github.com/munich-quantum-toolkit/predictor/search?q=is%3Aissue&type=issues).
 
-        If you have general questions, please consider [starting a discussion](https://github.com/cda-tum/mqt-predictor/discussions).
+        If you have general questions, please consider [starting a discussion](https://github.com/munich-quantum-toolkit/predictor/discussions).
   - type: textarea
     attributes:
       label: Environment information

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -8,7 +8,7 @@ body:
         **Thank you for wanting to suggest a feature for this project!**
 
         ⚠
-        Verify first that your idea is not [already requested on GitHub](https://github.com/cda-tum/mqt-predictor/search?q=is%3Aissue&type=issues).
+        Verify first that your idea is not [already requested on GitHub](https://github.com/munich-quantum-toolkit/predictor/search?q=is%3Aissue&type=issues).
 
   - type: textarea
     attributes:

.github/contributing.rst

@@ -6,7 +6,7 @@ We value contributions from people with all levels of experience.
 In particular if this is your first pull request not everything has to be perfect.
 We will guide you through the process.
 
-We use GitHub to `host code <https://github.com/cda-tum/mqt-predictor>`_, to `track issues and feature requests <https://github.com/cda-tum/mqt-predictor/issues>`_, as well as accept `pull requests <https://github.com/cda-tum/mqt-predictor/pulls>`_.
+We use GitHub to `host code <https://github.com/munich-quantum-toolkit/predictor>`_, to `track issues and feature requests <https://github.com/munich-quantum-toolkit/predictor/issues>`_, as well as accept `pull requests <https://github.com/munich-quantum-toolkit/predictor/pulls>`_.
 See https://docs.github.com/en/get-started/quickstart for a general introduction to working with GitHub and contributing to projects.
 
 Types of Contributions
@@ -15,16 +15,16 @@ Types of Contributions
 You can contribute in several ways:
 
 - 🐛 Report Bugs
-    Report bugs at https://github.com/cda-tum/mqt-predictor/issues using the *🐛 Bug report* issue template. Please make sure to fill out all relevant information in the respective issue form.
+    Report bugs at https://github.com/munich-quantum-toolkit/predictor/issues using the *🐛 Bug report* issue template. Please make sure to fill out all relevant information in the respective issue form.
 
 - 🐛 Fix Bugs
-    Look through the `GitHub Issues <https://github.com/cda-tum/mqt-predictor/issues>`_ for bugs. Anything tagged with "bug" is open to whoever wants to try and fix it.
+    Look through the `GitHub Issues <https://github.com/munich-quantum-toolkit/predictor/issues>`_ for bugs. Anything tagged with "bug" is open to whoever wants to try and fix it.
 
 - ✨ Propose New Features
-    Propose new features at https://github.com/cda-tum/mqt-predictor/issues using the *✨ Feature request* issue template. Please make sure to fill out all relevant information in the respective issue form.
+    Propose new features at https://github.com/munich-quantum-toolkit/predictor/issues using the *✨ Feature request* issue template. Please make sure to fill out all relevant information in the respective issue form.
 
 - ✨ Implement New Features
-    Look through the `GitHub Issues <https://github.com/cda-tum/mqt-predictor/issues>`_ for features. Anything tagged with "feature" is open to whoever wants to implement it. We highly appreciate external contributions to the project.
+    Look through the `GitHub Issues <https://github.com/munich-quantum-toolkit/predictor/issues>`_ for features. Anything tagged with "feature" is open to whoever wants to implement it. We highly appreciate external contributions to the project.
 
 - 📝 Write Documentation
     MQT Predictor could always use some more `documentation <https://mqt.readthedocs.io/projects/predictor>`_, and we appreciate any help with that.

.github/support.rst

@@ -1,12 +1,12 @@
 Support
 =======
 
-If you are stuck with a problem using MQT Predictor or have questions, please do get in touch at our `Issues <https://github.com/cda-tum/mqt-predictor/issues>`_ or `Discussions <https://github.com/cda-tum/mqt-predictor/discussions>`_. We'd love to help.
+If you are stuck with a problem using MQT Predictor or have questions, please do get in touch at our `Issues <https://github.com/munich-quantum-toolkit/predictor/issues>`_ or `Discussions <https://github.com/munich-quantum-toolkit/predictor/discussions>`_. We'd love to help.
 
 You can save time by following this procedure when reporting a problem:
 
 - Do try to solve the problem on your own first. Make sure to consult the `Documentation <https://mqt.readthedocs.io/projects/predictor>`_.
-- Search through past `Issues <https://github.com/cda-tum/mqt-predictor/issues>`_ to see if someone else already had the same problem.
+- Search through past `Issues <https://github.com/munich-quantum-toolkit/predictor/issues>`_ to see if someone else already had the same problem.
 - Before filing a bug report, try to create a minimal working example (MWE) that reproduces the problem. It's much easier to identify the cause for the problem if a handful of lines suffice to show that something isn't working.
 
 You can also always reach us at `quantum.cda@xcit.tum.de <mailto:quantum.cda@xcit.tum.de>`_.

.license-tools-config.json

@@ -0,0 +1,32 @@
+{
+  "author": {
+    "name": "Chair for Design Automation, TUM\nCopyright (c) 2025 Munich Quantum Software Company GmbH",
+    "years": [2023, 2025]
+  },
+  "force_author": true,
+  "license": "MIT",
+  "title": false,
+  "include": ["**/*"],
+  "style_override_for_suffix": {
+    ".pyi": "DOCSTRING_STYLE",
+    ".in": "POUND_STYLE",
+    ".mlir": "SLASH_STYLE",
+    ".td": "SLASH_STYLE",
+    ".yaml": "POUND_STYLE",
+    ".toml": "POUND_STYLE"
+  },
+  "exclude": [
+    "^\\.[^/]+",
+    "/\\.[^/]+",
+    ".*\\.md",
+    ".*\\.bib",
+    ".*\\.css",
+    ".*\\.ipynb",
+    ".*\\.json",
+    ".*\\.html",
+    "uv\\.lock",
+    ".*\\.rst",
+    "py\\.typed",
+    ".*build.*"
+  ]
+}

.pre-commit-config.yaml

@@ -70,6 +70,12 @@ repos:
       - id: blacken-docs
         additional_dependencies: [black==24.*]
 
+  # Check for license headers
+  - repo: https://github.com/emzeat/mz-lictools
+    rev: v2.7.0
+    hooks:
+      - id: license-tools
+
   # Format configuration files with prettier
   - repo: https://github.com/rbubley/mirrors-prettier
     rev: v3.5.3

LICENSE LICENSE.mdLICENSE renamed to LICENSE.md

@@ -1,16 +1,16 @@
 [![PyPI](https://img.shields.io/pypi/v/mqt.predictor?logo=pypi&style=flat-square)](https://pypi.org/project/mqt.predictor/)
 ![OS](https://img.shields.io/badge/os-linux%20%7C%20macos%20%7C%20windows-blue?style=flat-square)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square)](https://opensource.org/licenses/MIT)
-[![CI](https://img.shields.io/github/actions/workflow/status/cda-tum/mqt-predictor/ci.yml?branch=main&style=flat-square&logo=github&label=ci)](https://github.com/cda-tum/mqt-predictor/actions/workflows/ci.yml)
-[![CD](https://img.shields.io/github/actions/workflow/status/cda-tum/mqt-predictor/cd.yml?style=flat-square&logo=github&label=cd)](https://github.com/cda-tum/mqt-predictor/actions/workflows/cd.yml)
+[![CI](https://img.shields.io/github/actions/workflow/status/munich-quantum-toolkit/predictor/ci.yml?branch=main&style=flat-square&logo=github&label=ci)](https://github.com/munich-quantum-toolkit/predictor/actions/workflows/ci.yml)
+[![CD](https://img.shields.io/github/actions/workflow/status/munich-quantum-toolkit/predictor/cd.yml?style=flat-square&logo=github&label=cd)](https://github.com/munich-quantum-toolkit/predictor/actions/workflows/cd.yml)
 [![Documentation](https://img.shields.io/readthedocs/mqt-predictor?logo=readthedocs&style=flat-square)](https://mqt.readthedocs.io/projects/predictor)
-[![codecov](https://img.shields.io/codecov/c/github/cda-tum/mqt-predictor?style=flat-square&logo=codecov)](https://codecov.io/gh/cda-tum/mqt-predictor)
+[![codecov](https://img.shields.io/codecov/c/github/munich-quantum-toolkit/predictor?style=flat-square&logo=codecov)](https://codecov.io/gh/munich-quantum-toolkit/predictor)
 
 <p align="center">
   <a href="https://mqt.readthedocs.io">
    <picture>
-     <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/munich-quantum-toolkit/.github/refs/heads/main/docs/_static/mqt-banner-dark.svg" width="90%">
-     <img src="https://raw.githubusercontent.com/munich-quantum-toolkit/.github/refs/heads/main/docs/_static/mqt-banner-light.svg" width="90%" alt="MQT Banner">
+     <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/munich-quantum-toolkit/.github/refs/heads/main/docs/_static/logo-mqt-dark.svg" width="60%">
+     <img src="https://raw.githubusercontent.com/munich-quantum-toolkit/.github/refs/heads/main/docs/_static/logo-mqt-light.svg" width="60%" alt="MQT Logo">
    </picture>
   </a>
 </p>
@@ -41,13 +41,29 @@ For more details, please refer to:
   </a>
 </p>
 
-MQT Predictor is part of the [Munich Quantum Toolkit (MQT)](https://mqt.readthedocs.io/) developed by the [Chair for Design Automation](https://www.cda.cit.tum.de/) at the [Technical University of Munich](https://www.tum.de/).
+## Contributors and Supporters
 
-If you have any questions, feel free to create a [discussion](https://github.com/cda-tum/mqt-predictor/discussions) or an [issue](https://github.com/cda-tum/mqt-predictor/issues) on [GitHub](https://github.com/cda-tum/mqt-predictor).
+The _[Munich Quantum Toolkit (MQT)](https://mqt.readthedocs.io)_ is developed by the [Chair for Design Automation](https://www.cda.cit.tum.de/) at the [Technical University of Munich](https://www.tum.de/) and supported by the [Munich Quantum Software Company (MQSC)](https://munichquantum.software).
+Among others, it is part of the [Munich Quantum Software Stack (MQSS)](https://www.munich-quantum-valley.de/research/research-areas/mqss) ecosystem, which is being developed as part of the [Munich Quantum Valley (MQV)](https://www.munich-quantum-valley.de) initiative.
+
+<p align="center">
+  <picture>
+   <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/munich-quantum-toolkit/.github/refs/heads/main/docs/_static/mqt-logo-banner-dark.svg" width="90%">
+   <img src="https://raw.githubusercontent.com/munich-quantum-toolkit/.github/refs/heads/main/docs/_static/mqt-logo-banner-light.svg" width="90%" alt="MQT Partner Logos">
+  </picture>
+</p>
+
+Thank you to all the contributors who have helped make MQT Predictor a reality!
+
+<p align="center">
+<a href="https://github.com/munich-quantum-toolkit/predictor/graphs/contributors">
+  <img src="https://contrib.rocks/image?repo=munich-quantum-toolkit/predictor" />
+</a>
+</p>
 
 ## Getting Started
 
-`mqt-predictor` is available via [PyPI](https://pypi.org/project/mqt.predictor/).
+`mqt.predictor` is available via [PyPI](https://pypi.org/project/mqt.predictor/).
 
 ```console
 (venv) $ pip install mqt.predictor
@@ -59,7 +75,7 @@ The following code gives an example on the usage:
 from mqt.predictor import qcompile
 from mqt.bench import get_benchmark
 
-# get a benchmark circuit on algorithmic level representing the GHZ state with 5 qubits from [MQT Bench](https://github.com/cda-tum/mqt-bench)
+# get a benchmark circuit on algorithmic level representing the GHZ state with 5 qubits from [MQT Bench](https://github.com/munich-quantum-toolkit/bench)
 qc_uncompiled = get_benchmark(benchmark_name="ghz", level="alg", circuit_size=5)
 
 # compile it using the MQT Predictor
@@ -98,6 +114,8 @@ In case you are using MQT Predictor in your work, we would be thankful if you re
 }
 ```
 
+---
+
 ## Acknowledgements
 
 This project received funding from the European Research Council (ERC) under the European Union's Horizon 2020 research

README.md

@@ -51,5 +51,5 @@ We trained one RL model for each currently :ref:`supported quantum device <suppo
 
 Training Data
 -------------
-To train the model, sufficient training data must be provided as qasm files in the `respective directory <https://github.com/cda-tum/mqt-predictor/tree/main/src/mqt/predictor/rl/training_data/training_circuits>`_.
-We provide the training data used for the initial performance evaluation of this framework which are stored `here <https://github.com/cda-tum/mqt-predictor/tree/main/src/mqt/predictor/rl/training_data/trained_model>`_.
+To train the model, sufficient training data must be provided as qasm files in the `respective directory <https://github.com/munich-quantum-toolkit/predictor/tree/main/src/mqt/predictor/rl/training_data/training_circuits>`_.
+We provide the training data used for the initial performance evaluation of this framework which are stored `here <https://github.com/munich-quantum-toolkit/predictor/tree/main/src/mqt/predictor/rl/training_data/trained_model>`_.

docs/Compilation.rst

@@ -6,7 +6,7 @@ Ready to contribute to the project? Here is how to set up a local development en
 Initial Setup
 #############
 
-1. Fork the `cda-tum/mqt-predictor <https://github.com/cda-tum/mqt-predictor>`_ repository on GitHub (see https://docs.github.com/en/get-started/quickstart/fork-a-repo).
+1. Fork the `munich-quantum-toolkit/predictor <https://github.com/munich-quantum-toolkit/predictor>`_ repository on GitHub (see https://docs.github.com/en/get-started/quickstart/fork-a-repo).
 
 2. Clone your fork locally