HOW_WE_USE_GITHUB.md: Updates to working with issues, labeling and other general updates
#728
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added section on Working on Tickets; updated information on labels to highlight mandatory labels, include information on label descriptions and provide a general overview of the three mandatory label categories; separated out information on the process of issue sorting from information on what information sorting actually is; added information on spikes; changed infra --> infrastructure, in line with current repo name
conda-bot
added
the
cla-signed
for more information, see https://pre-commit.ci
kenodegard
requested changes
Mar 15, 2023
travishathaway
previously requested changes
Mar 16, 2023
kalawac
changed the title
changed link to global labels workflow to link to labels page, along with instructions for how to get to each repo's labels page
doubtful it will work tbh
for more information, see https://pre-commit.ci
kenodegard
requested changes
Mar 22, 2023
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
travishathaway
dismissed
their stale review
It's my review. I don't want it to hold anything up.
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
beeankha
reviewed
Apr 5, 2023
Co-authored-by: Bianca Henderson <beeankha@gmail.com>
kenodegard
changed the title
HOW_WE_USE_GITHUB.md: Updates to working with tickets, labeling and general updates
kenodegard
previously approved these changes
Apr 28, 2023
beeankha
previously approved these changes
Apr 28, 2023
jezdez
requested changes
Apr 28, 2023
|
@jezdez good call on conforming to using issue and not ticket I remember struggling with this since its weird talking about a feature request as an issue or phrasing things like "if you have an issue, open an issue" |
kenodegard
changed the title
HOW_WE_USE_GITHUB.md: Updates to working with tickets, labeling and general updatesHOW_WE_USE_GITHUB.md: Updates to working with issues, labeling and other general updates
Co-authored-by: Jannis Leidel <jannis@leidel.info>
Co-authored-by: Katherine Kinnaman <kkinnaman@anaconda.com>
jezdez
approved these changes
Apr 28, 2023
beeankha
approved these changes
Apr 28, 2023
kenodegard
dismissed
kathatherine’s stale review
suggested changes were incorporated
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added section to
How_We_Use_Github.mdon Working on Tickets; updated information on labels to highlight mandatory labels, include information on label descriptions and provide a general overview of the three mandatory label categories; separated out information on the process of issue sorting from information on what information sorting actually is; added information on spikes; changed infra --> infrastructure, in line with current repo nameDescription
Resolves #677
Working on Tickets, beginning on line 293)source::* labels(see sectionWhat labels are required for each issue?, beginning on line 160)