Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change references from "master" branch to "main" branch #1360

Merged
merged 15 commits into from
Aug 4, 2021
Merged

Conversation

willschlitzer
Copy link
Contributor

@willschlitzer willschlitzer commented Jun 25, 2021

As discussed in #1356, PyGMT is changing its default branch from "master" to "main". This pull request changes the references to "master" in the CI job files, maintenance.md, and the README.

Fixes #1356

Reminders

  • Run make format and make check to make sure the code follows the style guide.
  • Add tests for new features or tests that would have caught the bug that you're fixing.
  • Add new public functions/methods/classes to doc/api/index.rst.
  • Write detailed docstrings for all functions/methods.
  • If adding new functionality, add an example to docstrings or tutorials.

Slash Commands

You can write slash commands (/command) in the first line of a comment to perform
specific operations. Supported slash commands are:

  • /format: automatically format and lint the code
  • /test-gmt-dev: run full tests on the latest GMT development version

@willschlitzer willschlitzer added the maintenance Boring but important stuff for the core devs label Jun 25, 2021
@willschlitzer willschlitzer added this to the 0.5.0 milestone Jun 25, 2021
@willschlitzer willschlitzer self-assigned this Jun 25, 2021
.github/workflows/ci_tests_dev.yaml Outdated Show resolved Hide resolved
.github/workflows/ci_tests_dev.yaml Outdated Show resolved Hide resolved
@@ -44,7 +44,7 @@ jobs:
run: |
echo -e "## Summary of changed images\n" > report.md
echo -e "This is an auto-generated report of images that have changed on the DVC remote\n" >> report.md
dvc diff --show-md master HEAD >> report.md
dvc diff --show-md main HEAD >> report.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reminds me, we'll need to rename the 'master' branch on https://dagshub.com/GenericMappingTools/pygmt to 'main' too.

doc/maintenance.md Outdated Show resolved Hide resolved
doc/maintenance.md Outdated Show resolved Hide resolved
@maxrjones
Copy link
Member

While GitHub will redirect links, I think we should update the links in these files to reflect the new main name as part of this process:

./doc/install.rst
./doc/conf.py
./pygmt/src/x2sys_cross.py
./doc/contributing.md
./doc/external_resources.md
./.github/config.yml

@willschlitzer
Copy link
Contributor Author

While GitHub will redirect links, I think we should update the links in these files to reflect the new main name as part of this process:

./doc/install.rst
./doc/conf.py
./pygmt/src/x2sys_cross.py
./doc/contributing.md
./doc/external_resources.md
./.github/config.yml

./doc/install.rst and ./pygmt/src/x2sys_cross.py
It looks like the only instance of master is in reference to the GMT branch

@maxrjones
Copy link
Member

While GitHub will redirect links, I think we should update the links in these files to reflect the new main name as part of this process:

./doc/install.rst
./doc/conf.py
./pygmt/src/x2sys_cross.py
./doc/contributing.md
./doc/external_resources.md
./.github/config.yml

./doc/install.rst and ./pygmt/src/x2sys_cross.py
It looks like the only instance of master is in reference to the GMT branch

sounds good, I did a quick search but didn't spend much time checking the references.

@willschlitzer willschlitzer marked this pull request as ready for review June 29, 2021 10:03
@willschlitzer willschlitzer modified the milestones: 0.5.0, 0.4.1 Jul 24, 2021
@seisman
Copy link
Member

seisman commented Jul 30, 2021

Maybe we should give this PR a final review and merge it several days before the v0.4.1 release, so that we can have more time to check if there are any related issues in the upcoming v0.4.1 release.

@core-man core-man mentioned this pull request Jul 31, 2021
23 tasks
doc/contributing.md Outdated Show resolved Hide resolved
@core-man
Copy link
Member

contributing.md still have sentences using master:

  • Line 98:
    our tests. This way, the *master* branch is always stable.
    
  • Line 173:
    See the [`environment.yml`](https://github.com/GenericMappingTools/pygmt/blob/master/environment.yml)
    

Copy link
Member

@core-man core-man left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think all "master" are changed to "main" except in some places indicated above. Great~

Co-authored-by: Yao Jiayuan <[email protected]>
@weiji14
Copy link
Member

weiji14 commented Aug 1, 2021

Besides those mentioned at #1360 (comment), here's a few more:

@willschlitzer
Copy link
Contributor Author

@weiji14 @core-man I made the changes you requested

@seisman
Copy link
Member

seisman commented Aug 3, 2021

Besides those mentioned at #1360 (comment), here's a few more:

I don't think we can change master_doc to main_doc. It's a sphinx configuration and is used internally by sphinx (see https://github.com/sphinx-doc/sphinx/search?q=master_doc).

EDIT: Sphinx has renamed master_doc to root_doc in sphinx v4.0. We can change master_doc to root_doc here, but it means PyGMT will require sphinx >= 4.0, which was release in May, 2021.

Copy link
Member

@weiji14 weiji14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides those mentioned at #1360 (comment), here's a few more:

I don't think we can change master_doc to main_doc. It's a sphinx configuration and is used internally by sphinx (see https://github.com/sphinx-doc/sphinx/search?q=master_doc).

EDIT: Sphinx has renamed master_doc to root_doc in sphinx v4.0. We can change master_doc to root_doc here, but it means PyGMT will require sphinx >= 4.0, which was release in May, 2021.

Was just about to say that root_doc should be used instead. We have sphinx 4.1.2 in CI (https://github.com/GenericMappingTools/pygmt/runs/3235302620?check_suite_focus=true#step:6:187) so it should be fine.

doc/conf.py Outdated Show resolved Hide resolved
doc/_templates/layout.html Outdated Show resolved Hide resolved
Copy link
Member

@maxrjones maxrjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this get merged before or after the actual renaming of the branch?

@seisman
Copy link
Member

seisman commented Aug 4, 2021

Does this get merged before or after the actual renaming of the branch?

Either should work. I prefer to merge this PR after renaming the branch, so that we can immediately know how renaming the main branch affects PRs.

@maxrjones
Copy link
Member

Does this get merged before or after the actual renaming of the branch?

Either should work. I prefer to merge this PR after renaming the branch, so that we can immediately know how renaming the main branch affects PRs.

OK, I can rename the branch after the current workflows finish and then ping here to merge in the PR.

@maxrjones
Copy link
Member

maxrjones commented Aug 4, 2021

Looks good to merge after checks pass, thanks @willschlitzer!

@weiji14
Copy link
Member

weiji14 commented Aug 4, 2021

Looks good to merge after checks pass, thanks @willschlitzer!

Thanks heaps @willschlitzer! I'll squash and merge this in directly since the "master" -> "main" rename has been done (otherwise the links on https://www.pygmt.org/dev/index.html won't work).

@weiji14 weiji14 merged commit 9cbda9e into main Aug 4, 2021
@weiji14 weiji14 deleted the new-main-branch branch August 4, 2021 23:54
sixy6e pushed a commit to sixy6e/pygmt that referenced this pull request Dec 21, 2022
…ngTools#1360)

PyGMT is changing its default branch from "master" to "main".
This pull request changes the references to "master" in the CI
job files, maintenance.md, and the README.

* change workflow files to point to "main" branch instead of "master" branch
* change README to use "main" branch instead of "master" branch
* change maintenance.md use "main" branch instead of "master" branch
* update conf.py to use main instead of master
* update contributing.md to use main instead of master
* update external_resources.md to use main instead of master
* update config.yml to use main instead of master
* change master_doc to root_doc in conf.py and layout.html

Co-authored-by: Wei Ji <[email protected]>
Co-authored-by: Dongdong Tian <[email protected]>
Co-authored-by: Yao Jiayuan <[email protected]>
Co-authored-by: Meghan Jones <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Boring but important stuff for the core devs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change main branch from "master" to "main"
5 participants