Hello! 👋 Thanks for opening your first pull request here! ❤️ We will try to get back to you soon. 🚴🏽‍♂️

Hey there!
I'm really new to contributing like this, and would love some help.

I can't seem to understand the failed build doc tests here, since there was only a minor adjustment to the doc, and it seems to match the requested syntax.
It seems to be related to the Azure pipeline, which I might have some difficulty troubleshooting. I'm currently working on a mac, and if I understand correctly, this is a Windows specific pipeline?

I'm really new to contributing like this, and would love some help.

Thanks for asking for help!

I can't seem to understand the failed build doc tests here, since there was only a minor adjustment to the doc, and it seems to match the requested syntax. It seems to be related to the Azure pipeline, which I might have some difficulty troubleshooting. I'm currently working on a mac, and if I understand correctly, this is a Windows specific pipeline?

Looking at the CI runs for commit ab19cca, there were two things going on:

• C:\Miniconda\lib\site-packages\sphinxcontrib\bibtex\transforms.py:59: PendingDeprecationWarning: nodes.Node.traverse() is obsoleted by Node.findall(). https://dev.azure.com/mne-tools/mne-python/_build/results?buildId=20802&view=logs&j=c04f1cb7-a28e-5e8a-4074-704b3a6c72b1&t=c5a3e5f7-2b1e-57e1-93fb-c99e1ea8bb1a&l=1135 This problem was unrelated to your PR, and was solved by @hoechenberger merging in changes from main (in other words, that particular CI problem was fixed by someone else, but your PR didn't have that fix on it until @hoechenberger merged main here)
• changes/latest.inc:26: WARNING: py:func reference target not found: mne.channels.montage.DigMontage.__eq__ https://dev.azure.com/mne-tools/mne-python/_build/results?buildId=20802&view=logs&j=c04f1cb7-a28e-5e8a-4074-704b3a6c72b1&t=c5a3e5f7-2b1e-57e1-93fb-c99e1ea8bb1a&l=1968 This is a genuine problem with your PR. You cannot cross-reference any old function within MNE-Python: only functions/methods/classes that are listed in doc/python_reference.rst are allowable cross-reference targets. So linking to the __eq__ method would only work if you added it to that file (but we don't want that, we don't typically put private/builtin methods there). @hoechenberger fixed this by editing the changelog entry to not include a crossreference to __eq__
• The other failures (on CircleCI, e.g. here) are the same errors seen on the SphinxWindows job on Azure --- we test the same things on multiple platforms so often one mistake leads to 2 or 3 CI failures.