Consider including a link to Azure templates

[astrofrog]

Building on top of cibuildwheel, @Cadair and I have developed an Azure template that makes it very easy for developers to add wheel and sdist building to their repositories:

https://github.com/OpenAstronomy/azure-pipelines-templates/

With this template, the Azure configuration can look as simple as:

jobs:
- template: publish.yml@OpenAstronomy
  parameters:
    pypi_connection_name: 'pypi_endpoint'
    targets:
    - sdist
    - wheels_linux
    - wheels_macos
    - wheels_windows

But still allows the CIBW env variables to be set if needed. I thought it might be worth linking to this from the README here? (but feel free to close if not)

[henryiii]

Wait, can you load a remote template in Azure? With parameters? https://github.com/scikit-hep/azure-wheel-helpers would likely have lasted longer if I knew about this (but probably best I didn't, as the transition to cibuildwheel has been fantastic). (or maybe it's a newer feature)

Also, there are lots of thumbs up, so maybe you could propose the wording to use as a note in the Azure section? Also, what does "opinionated" mean? That should probably be noted a bit better in the README or in the note. Do you have to use tox, PEP 517, etc.

Just posting it here is fine, I can copy it to the docs. I'm working on something that might help here, too.

[joerick]

I nearly considered using a template as the 'minimal config' in cibuildwheel, but I decided in the end that it's better to spell it out natively, so there isn't a 'config eject' moment, where a small tweak requires a large change away from the template to a native approach.

But, I expect for many people a template would do just fine. However, I do hesitate to include this in our docs as a first-party example because these templates have their own 'API' and docs - https://openastronomy-azure-pipelines.readthedocs.io/en/latest/publish.html . Perhaps, a link out to their docs site from the Azure setup section would be more appropriate.

[Cadair]

I also think a link to the docs would be the best option.