Frank Harkins

Python 2 was sunset a while ago, although I think a simple `__future__` import might let this work with both. Let me try tonight.

This seems to be a problem in the coupling map returned for `simulator_stabilizer`: ```python response = requests.request( "GET", "https://api.quantum-computing.ibm.com/runtime/backends/simulator_stabilizer/configuration", headers={ "Accept": "application/json", "Authorization": "Bearer " }, ) response.json()["gates"][0] ``` ```...

Even worse is that if the circuit is created with `ClassicalRegister` arguments (rather than `int`s), the job completes but with nonsense results: | backend | cbit? | values |---------|-------|-------------------------- |...

We have a `Circuit simulator` tag for that purpose. However I've since realised we already have a `Hardware` tag that means something else. Maybe these get a `Hardware provider` tag?...

> Hm, what does it mean? "For quantum hardware design or quantum control". We could expand the definition though

Yes please, that would be great. I've assigned you 🙂 Let me know if you have any questions.

Thanks for this @mickahell! 🚀 Rather than a composite action, what do you think of a template that developers can copy and paste into their projects, and adjust as needed?...

> Too much text and commande for someone who never use Actions We can include comments to explain which bits to modify, for example: ```yaml - name: Run tests run:...

> ...they can just don't put any test at all and submit whatever they want and we could have a bunch list of unworking project without knowing. IMO the review...

This was mostly addressed in #701; there are now only two "sources of truth" (the template and the repository model), but we have a test to make sure they stay...