Add slash command '/test-gmt-dev' to test GMT dev version

[seisman]

Description of proposed changes

This PR adds the slash command /test-gmt-dev which can trigger the GMT Dev Tests workflow. So we can test GMT master branch anytime, without requesting reviews from other maintainers or teams (Also fixes #828).

As you may know/remember, the slash command can only read the configurations in the master branch, so we can't test this PR unless we merge it into the master branch.

To test this PR, I forked the PyGMT repository to my own account (https://github.com/seisman/pygmt), and made changes directly to my own master branch.

If you compare my master branch and the PyGMT master branch, you will see my master branch is 2 commits ahead of PyGMT master branch. The two commits are:

• seisman@11446e2: This commit is the same as the only commit in this PR
• seisman@37f83e4: The slash command uses the GenericMappingTools bot to generate a token, which is not available in my own fork. So I have to use my own token instead. This commit is necessary in my own fork for testing purposes.

To confirm that everything works well, I opened an example PR in my own fork (https://github.com/seisman/pygmt/pull/2). Please go to that PR to see how it works.

TODO:

• Remove review_requested condition from the workflow, so that we can run the GMT Latest Tests workflow by marking it "ready for review", or using the slash command /test-gmt-dev (done in 4a22c59)
• Update the [pull request template] (https://github.com/GenericMappingTools/pygmt/blob/master/.github/PULL_REQUEST_TEMPLATE.md) (done in 8620bab)
• Update contributing guide or maintenance guide (done in ef31c15)

Known issues:

The "GMT Latest Tests" triggered by /test-gmt-master won't show the workflow status in the status summary page (like the screenshot below), so we have to go the the "Actions" page to find the testing results.

Note: you may find the following status page in PR https://github.com/seisman/pygmt/pull/2. These "GMT Latest Tests" status were triggered by "mark it ready for review", not by the slash command /test-gmt-master.

One possible solution is: when the workflow is triggered by slash commands, we can let the workflow leave a comment saying that "The workflow is running at https://github.com/GenericMappingTools/pygmt/actions/runs/XXXXX"

Fixes #828.

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.

Notes

• You can write /format in the first line of a comment to lint the code automatically

[weiji14]

Please also update the part in https://github.com/GenericMappingTools/pygmt/blob/v0.2.1/MAINTENANCE.md#github-actions which says:

ci_tests_dev.yaml (GMT Latest Tests on Linux/macOS/Windows).

This is only triggered when a review is requested or re-requested on a PR. It is also scheduled to run daily on the master branch.

to mention that the test can also be triggered using /test-gmt-master.

Note: you may find the following status page in PR seisman#2. These "GMT Latest Tests" status were triggered by "mark it ready for review", not by the slash command /test-gmt-master.
image
One possible solution is: when the workflow is triggered by slash commands, we can let the workflow leave a comment saying that "The workflow is running at https://github.com/GenericMappingTools/pygmt/actions/runs/XXXXX"

Might be complicated trying to code up the chatbot comment (though it will be nice, if not a bit annoying). How often will we need to keep triggering GMT Latest Tests? If it's not too often I think it's fine to just navigate to the Actions tab manually.

[seisman]

Might be complicated trying to code up the chatbot comment (though it will be nice, if not a bit annoying). How often will we need to keep triggering GMT Latest Tests? If it's not too often I think it's fine to just navigate to the Actions tab manually.

We probably only want to trigger the GMT Latest Tests when a PR is close to merging. We can navigate to the Actions tab manually and see how it goes.

[weiji14]

Suggested change

	test-gmt-master
	test-gmt-dev

What do you think about changing the name to 'latest' to match the Github Actions name?

[seisman]

When we say "the latest GMT", we usually mean "the latest stable GMT release" (i.e., 6.1.1).

What about "GMT Dev Tests" and /test-gmt-dev?

[weiji14]

Yep, dev sounds good and is shorter. Please remember to change the PR title too.

[seisman]

Done in 6df8e34 and 72b7dfa