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.

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

Replace all "good second issue" labels with "good first issue" label on open PRs and Issues #4431

Closed
1 of 10 tasks
Tracked by #4423
ExperimentsInHonesty opened this issue Apr 6, 2023 · 2 comments
Closed
1 of 10 tasks
Tracked by #4423
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Dependency An issue is blocking the completion or starting of another issue Draft Issue is still in the process of being created Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 6, 2023

Dependency

Overview

Dev leads determined that having to separate "good first issues" and "good second issues" does not make much sense since the corresponding issues are essentially the same complexity. We need to replace all the "good second issue" labels with "good first issue" labels so that dev leads do not need to juggle making enough of each issue.

Details

All the Closed PRs and Issues have already been changed

Action Items

  • Go to the issues with the good second issue label
  • If an issue has an assignee, post the following message on their issue
    Hi, we are about to change the label on your issue `Complexity: Good second issue` to `good first issue` to relect the update to our issue ladder of all members will work on two good first issues instead of the dev team making seperate issues for first and second (even though they were essentially the same).  
    
    You might be asking youself, why do you need to do two good first issues, instead of just one?!.  The first two issues is where we catch if anyone has problems with branching appropriately on our project.  So we intentionly make them very very small and perscriptive so that we can focus on making sure you have the branching down before we move you on to the bigger issues that get less and less perscriptive as you go up the ladder.
    
    When you sucessfully finish with this issue, you can go on to a Small issue just as you would have before.
    
  • Go back to the issue tab and your search,
    • Check the box at the top of the list to select the entire list
      • Click on "Label"
        • Deselect "good second issue"
        • Select "good first issue"
        • Click off the drop down, to make it take effect.

Resources/Instructions

@ExperimentsInHonesty ExperimentsInHonesty added 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 role: dev leads Tasks for technical leads Draft Issue is still in the process of being created size: 0.25pt Can be done in 0.5 to 1.5 hours labels Apr 6, 2023
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Apr 6, 2023
@ExperimentsInHonesty ExperimentsInHonesty added role missing and removed role: dev leads Tasks for technical leads labels Apr 6, 2023
@ExperimentsInHonesty ExperimentsInHonesty added Dependency An issue is blocking the completion or starting of another issue ready for dev lead Issues that tech leads or merge team members need to follow up on labels Apr 6, 2023
@ExperimentsInHonesty
Copy link
Member Author

@jdingeman

@jdingeman jdingeman added role: back end/devOps Tasks for back-end developers and removed role missing labels Apr 7, 2023
@roslynwythe
Copy link
Member

@ExperimentsInHonesty I searched and could not find any open Issues or PRs with the label "good second issue", so closing this issue as not planned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Dependency An issue is blocking the completion or starting of another issue Draft Issue is still in the process of being created Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
Development

No branches or pull requests

3 participants