Skip to content

Add guidelines for managing issues to maintenance.md #1301

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.

Sign up for GitHub

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

Merged
merged 6 commits into from
May 28, 2021
Merged

Add guidelines for managing issues to maintenance.md #1301

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
2b5c3a6
Add guidelines for managing issues to maintenance.md
May 26, 2021
6a00e90
Wrap text and add milestones to issues guide
May 26, 2021
b3a5838
Fix grammar
May 26, 2021
80dff17
Update doc/maintenance.md
May 26, 2021
4e0c7f6
Update doc/maintenance.md
May 28, 2021
4818870
Merge branch 'master' into issues-guide
May 28, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions doc/maintenance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,21 @@ instead.
branch are in the `dev` folder. Pages for each release are in their own folders.
**Automatically updated by GitHub Actions** so you shouldn't have to make commits here.

## Managing GitHub issues

A few guidelines for managing GitHub issues:

* Assign [labels](https://github.com/GenericMappingTools/pygmt/labels) and the expected
[milestone](https://github.com/GenericMappingTools/pygmt/milestones) to issues as
appropriate.
* When people request to work on an open issue, either assign the issue to that person
and post a comment about the assignment or explain why you are not assigning the
issue to them and, if possible, recommend other issues for them to work on.
* People with write access should self-assign issues and/or comment on the issues that
they will address.
* For upstream bugs, close the issue after an upstream release fixes the bug. If
possible, post a comment when an upstream PR is merged that fixes the problem, and
consider adding a regression test for serious bugs.

## Reviewing and merging pull requests

Expand Down