Update links for GitHub org transfer

[maxrjones]

Description of proposed changes

Even though GitHub sets up redirects for the transferred repository, it will be more clear to have the links directly point to the xarray-contrib org. This PR updates all such links except in the demo and code of conduct, which require larger updates.

[weiji14]

This PR updates all such links except in the demo and code of conduct, which require larger updates.

Ok with leaving the Code of Conduct untouched since it points to https://github.com/pangeo-data/governance/blob/master/conduct/code_of_conduct.md and there's no equivalent in xarray-contrib. But for demo.ipynb, there's only 3 lines to update, could we not do it in this PR?

Also, small reminder to update the links on https://github.com/conda-forge/xbatcher-feedstock.

[maxrjones]

This PR updates all such links except in the demo and code of conduct, which require larger updates.

Ok with leaving the Code of Conduct untouched since it points to https://github.com/pangeo-data/governance/blob/master/conduct/code_of_conduct.md and there's no equivalent in xarray-contrib. But for demo.ipynb, there's only 3 lines to update, could we not do it in this PR?

I think the demo is rendered from static output stored in the notebook rather than executed when building the docs. So I want to check whether it still works since we've been moving some data around. I'll update the lines if there aren't any other changes required.

Also, small reminder to update the links on https://github.com/conda-forge/xbatcher-feedstock.

Thanks! I'll check on this as well as PyPI and codecov. Do you think it would be helpful to add these common to-do's as a checklist on the issue template for xarray-contrib?

[weiji14]

This PR updates all such links except in the demo and code of conduct, which require larger updates.

Ok with leaving the Code of Conduct untouched since it points to https://github.com/pangeo-data/governance/blob/master/conduct/code_of_conduct.md and there's no equivalent in xarray-contrib. But for demo.ipynb, there's only 3 lines to update, could we not do it in this PR?

I think the demo is rendered from static output stored in the notebook rather than executed when building the docs. So I want to check whether it still works since we've been moving some data around. I'll update the lines if there aren't any other changes required.

Ah yes, if there's a cache mechanism, then best to be careful. The links should still redirect properly though so it's not urgent.

Also, small reminder to update the links on https://github.com/conda-forge/xbatcher-feedstock.

Thanks! I'll check on this as well as PyPI and codecov. Do you think it would be helpful to add these common to-do's as a checklist on the issue template for xarray-contrib?

Mm, I wouldn't add it to the issue template to be honest (if you mean the transer-repo-to-this-organization template). It's probably better to leave it as a manual thing for maintainers to do 🙂