Skip to content

Conversation

@seisman
Copy link
Member

@seisman seisman commented Jan 6, 2024

Description of proposed changes

Similar to #2958.

Slash command /test-gmt-dev is no longer supported. To enable the "GMT Dev Tests" workflow, just add the run/test-gmt-dev label (needs written permission to this repository).

@seisman seisman added maintenance Boring but important stuff for the core devs run/test-gmt-dev Trigger the GMT Dev Tests workflow in PR labels Jan 6, 2024
@seisman seisman added this to the 0.11.0 milestone Jan 6, 2024
@seisman seisman added run/test-gmt-dev Trigger the GMT Dev Tests workflow in PR and removed run/test-gmt-dev Trigger the GMT Dev Tests workflow in PR labels Jan 6, 2024
@seisman seisman added the needs review This PR has higher priority and needs review. label Jan 7, 2024
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.

Just two comments, but should be ok if you have a good answer for it 😁

# branches: [ main ]
pull_request:
types: [ready_for_review]
types: [ labeled, synchronize ]
Copy link
Member

Choose a reason for hiding this comment

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

+1 to this. We originally set "GMT Dev Tests" to run when the PR is ready for review in PR #831, but that might have been a bit of a waste of CI resources to be honest.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've changed the types to types: [ opened, reopened, labeled, synchronize ], following PR #2958.

Comment on lines 21 to -27
**Slash Commands**

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

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

Choose a reason for hiding this comment

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

Similar to my comment at #2958 (comment), should we still document this somewhere so that contributors/maintainers know to request that the run/test-gmt-dev label gets added to PRs that require it? Or just rely on maintainers to know when to set the label?

Copy link
Member Author

Choose a reason for hiding this comment

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

@weiji14 weiji14 added final review call This PR requires final review and approval from a second reviewer and removed needs review This PR has higher priority and needs review. labels Jan 7, 2024
@seisman seisman merged commit af7892f into main Jan 7, 2024
@seisman seisman deleted the label-test-gmt-dev branch January 7, 2024 08:13
@seisman seisman removed the final review call This PR requires final review and approval from a second reviewer label Jan 7, 2024
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 run/test-gmt-dev Trigger the GMT Dev Tests workflow in PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants