Skip to content
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

Jump to bottom

ER: Replace all "good second issue" labels with "good first issue" label #4371

Closed
1 of 5 tasks
jdingeman opened this issue Apr 2, 2023 · 2 comments
Closed
1 of 5 tasks

ER: Replace all "good second issue" labels with "good first issue" label #4371

jdingeman opened this issue Apr 2, 2023 · 2 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Milestone
08. Team workflow

Comments

@jdingeman
Copy link
Member

jdingeman commented Apr 2, 2023 •
edited
Loading

Emergent Requirement - Problem

Dev Leads have decided that dealing with the "good second issue" is causing too many issues with making sure we have enough issues for devs to work on. We want to replace the "good second issue" label with "good first issue" on any issue that has the former label.

Date discovered

April 2, 2023

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@jdingeman
@ExperimentsInHonesty
@MattPereira
@roslynwythe

What happens if this is not addressed

We continue to struggle making enough good first AND good second issues

Resources

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]
@jdingeman jdingeman added the size: 0.25pt Can be done in 0.5 to 1.5 hours label Apr 2, 2023
@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Apr 2, 2023
@jdingeman jdingeman added this to the 08. Team workflow milestone Apr 2, 2023
@github-actions

This comment was marked as outdated.

Sign in to view
@jdingeman jdingeman added role: back end/devOps Tasks for back-end developers Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Complexity: Small Take this type of issues after the successful merge of your second good first issue ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing labels Apr 2, 2023
@jdingeman jdingeman mentioned this issue Apr 5, 2023
Closed
12 tasks
@jdingeman
Copy link
Member Author

New issue here:

@jdingeman jdingeman removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Apr 5, 2023
@JessicaLucindaCheng JessicaLucindaCheng added the ER Emergent Request label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
P: HfLA Website: Project Board
Archived in project
Milestone
08. Team workflow
Development

No branches or pull requests
2 participants
@JessicaLucindaCheng @jdingeman