Updates to triaging guide: Issue prioritization and high-level triage workflow by asteiker · Pull Request #1308 · earthaccess-dev/earthaccess

asteiker · 2026-04-20T20:26:06Z

Description

Resolves #1070 and based on recent discussions at the Collab cafe with @saberbrasher on incorporating prioritization best practices, GitHub project management, and overall triaging workflow into the Triaging Guide.

This guide now begins with an issue lifecycle overview, and describes those lifecycle steps in detail with a focus on issue triaging and prioritization. This guide is also meant to help contributors understand our prioritization process and criteria, and how to find prioritized issues in our GitHub project.

"Ready for review" checklist

Place this Pull Request (PR) in draft until it is ready for review (see below)
Please review our Pull Request Guide
Mark "ready for review" after following instructions in the guide

Merge checklist

[ x] PR title is descriptive
[ x] PR body contains links to related and resolved issues (e.g. closes #1)
If needed, CHANGELOG.md updated
If needed, docs and/or README.md updated
If needed, unit tests added (unsure how? see below!)
All checks passing (tip: comment pre-commit.ci autofix if pre-commit is failing)
At least one approval

📚 Documentation preview 📚: https://earthaccess--1308.org.readthedocs.build/en/1308/

github-actions · 2026-04-20T20:26:17Z

👈 Launch a binder notebook on this branch for commit b5c4f68

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit 6d9e0d5

👈 Launch a binder notebook on this branch for commit 420fd25

👈 Launch a binder notebook on this branch for commit 6e5ce75

👈 Launch a binder notebook on this branch for commit 0ef563d

👈 Launch a binder notebook on this branch for commit f200646

👈 Launch a binder notebook on this branch for commit 1aff0da

👈 Launch a binder notebook on this branch for commit 4bb4454

👈 Launch a binder notebook on this branch for commit 7e0512a

👈 Launch a binder notebook on this branch for commit dd8c8a9

👈 Launch a binder notebook on this branch for commit 64e87fb

👈 Launch a binder notebook on this branch for commit 6fa0d59

👈 Launch a binder notebook on this branch for commit 6baeaad

👈 Launch a binder notebook on this branch for commit 3c417b7

👈 Launch a binder notebook on this branch for commit 82ef24c

👈 Launch a binder notebook on this branch for commit 6fa0e8a

👈 Launch a binder notebook on this branch for commit fea58d6

👈 Launch a binder notebook on this branch for commit a83b5d5

👈 Launch a binder notebook on this branch for commit 3af6ba0

👈 Launch a binder notebook on this branch for commit 3653f4a

👈 Launch a binder notebook on this branch for commit 83ac905

👈 Launch a binder notebook on this branch for commit 213e1d5

👈 Launch a binder notebook on this branch for commit 56ca933

👈 Launch a binder notebook on this branch for commit 047504a

👈 Launch a binder notebook on this branch for commit 2c6a087

👈 Launch a binder notebook on this branch for commit 8c23914

👈 Launch a binder notebook on this branch for commit 6a62194

👈 Launch a binder notebook on this branch for commit c88aa00

👈 Launch a binder notebook on this branch for commit dee3985

👈 Launch a binder notebook on this branch for commit 5e1d26e

👈 Launch a binder notebook on this branch for commit 47239a2

👈 Launch a binder notebook on this branch for commit 39a0621

👈 Launch a binder notebook on this branch for commit c8208d2

👈 Launch a binder notebook on this branch for commit ad67682

mfisher87 · 2026-04-21T19:00:39Z

Nice work! 🤩

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

mfisher87 · 2026-04-23T02:12:05Z

@asteiker just in case you didn't see them, many of my comments are hidden because I did too many 🫣

saberbrasher

Awesome work on this @asteiker and @mfisher87 !! I have a few comments/ questions, but you two definitely did the heavy lifting.

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

asteiker · 2026-07-07T23:28:50Z

@mfisher87 @saberbrasher I have moved this out of draft and is ready for your re-review! @Sherwin-14 there were a few minor changes made to the workflow diagram so I wanted to make sure you have an opportunity to review as well. It looks like there are conflicts that will need to be resolved but maybe this can be done once it's ready to merge.

saberbrasher

A quick initial review! This is looking great, Amy!

saberbrasher · 2026-07-08T22:58:26Z

+**We hope that this guide will empower anyone to contribute to issue triaging, and address a common question for contributors: "I'm interested in working on the highest priority issues that will solve important problems facing the `earthaccess` community. Where do I begin?"**

-When labeling an issue, choose the label(s) that best describes the issue. Using labels consistently and accurately ensures that issues are trackable and searchable.
+See the [Issue grooming](#issue-grooming) section below for details on how to identify and browse prioritized issues via the [`earthaccess` GitHub Project](https://github.com/orgs/earthaccess-dev/projects/1).


I suggest we maybe call this section "Issue prioritization" to be in line with the title of the page.

Right now this section sort of blends in/ gets lost with all the other text. I wonder if putting it in a nice little info box could add a visual separation, and then adding something like:
"Want to start working quickly?" before the "see this section for details...." content might draw attention to it.

saberbrasher · 2026-07-08T23:04:58Z

+
+## Working issues
+
+- [Assign](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users) the issue to the implementer.


Doesn't this happen automatically for this library? I don't remember ever having to assign myself. I suppose the person creating the issue may not be the person who solves it, but in that case, there would be a PR created by someone else (which would be assigned to the PR creator).

I am not aware of the Issue assignments happening automatically. Are you thinking about a workflow where a PR is submitted, and then the related Issue is linked? Is that where you would expect the Issue to get automatically assigned based on the PR assignment? Otherwise how would this be auto-assigned if the issue was in work?

oops, ignore this comment! I was getting the issue assignment functionality here in GitHub mixed up with another tool.

Co-authored-by: Saber Brasher <134096880+saberbrasher@users.noreply.github.com>

asteiker added 9 commits April 6, 2026 15:22

update goal and scope

e25c68c

add tip callout

66cd0f6

draft updated outline

e25e557

update broken link

5d97781

add issue lifecycle outlne

e7935bd

issue prioritization outline

990c5bc

update triage workflow and labels

dd4b9a4

update label section

7092656

add prioritization section

b5c4f68

asteiker requested a review from saberbrasher April 20, 2026 20:26

mfisher87 reviewed Apr 21, 2026

View reviewed changes

asteiker and others added 8 commits April 22, 2026 17:18

Update docs/contributor/triaging.md

6d9e0d5

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

420fd25

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

6e5ce75

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

0ef563d

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

f200646

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

1aff0da

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

4bb4454

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

7e0512a

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

saberbrasher reviewed Apr 23, 2026

View reviewed changes

asteiker and others added 7 commits May 18, 2026 08:53

Update docs/contributor/triaging.md

dd8c8a9

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

64e87fb

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

6fa0d59

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Update docs/contributor/triaging.md

6baeaad

Co-authored-by: Matt Fisher <3608264+mfisher87@users.noreply.github.com>

Clarify community manager role in GH project

3c417b7

Update triaging role language.

82ef24c

Remove issue vs discussion content

6fa0e8a

asteiker added 13 commits June 9, 2026 12:33

Update sub-bullet formatting.

fea58d6

fix RTD bullet formatting

a83b5d5

Re-label lifecycle detail sections

3af6ba0

reorg triaging sections and content

3653f4a

Update new issue guidance

83ac905

Remove label descriptions

213e1d5

Update grooming guidance

56ca933

Increase workflow headers so TOC shows up

047504a

Remove needs reproduction label in workflow diagram

2c6a087

Add grooming header link

8c23914

Update header link to mkdown format

6a62194

Update header link

c88aa00

Add project view details

dee3985

asteiker requested review from Sherwin-14, mfisher87 and saberbrasher July 7, 2026 23:26

asteiker marked this pull request as ready for review July 7, 2026 23:26

saberbrasher reviewed Jul 8, 2026

View reviewed changes

asteiker and others added 5 commits July 14, 2026 12:16

Update docs/contributor/triaging.md

5e1d26e

Co-authored-by: Saber Brasher <134096880+saberbrasher@users.noreply.github.com>

Update docs/contributor/triaging.md

47239a2

Co-authored-by: Saber Brasher <134096880+saberbrasher@users.noreply.github.com>

Update docs/contributor/triaging.md

39a0621

Co-authored-by: Saber Brasher <134096880+saberbrasher@users.noreply.github.com>

Update docs/contributor/triaging.md

c8208d2

Co-authored-by: Saber Brasher <134096880+saberbrasher@users.noreply.github.com>

Update triaging.md with info callout for contributors

ad67682


		## Working issues

		- [Assign](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/assigning-issues-and-pull-requests-to-other-github-users) the issue to the implementer.

Uh oh!

Conversation

asteiker commented Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

"Ready for review" checklist

Merge checklist

Uh oh!

github-actions Bot commented Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mfisher87 commented Apr 21, 2026

Uh oh!

mfisher87 commented Apr 23, 2026

Uh oh!

saberbrasher left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

asteiker commented Jul 7, 2026

Uh oh!

saberbrasher left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

saberbrasher Jul 8, 2026

Choose a reason for hiding this comment

Uh oh!

saberbrasher Jul 8, 2026

Choose a reason for hiding this comment

Uh oh!

saberbrasher Jul 8, 2026

Choose a reason for hiding this comment

Uh oh!

asteiker Jul 14, 2026

Choose a reason for hiding this comment

Uh oh!

saberbrasher Jul 14, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

asteiker commented Apr 20, 2026 •

edited

Loading

github-actions Bot commented Apr 20, 2026 •

edited

Loading