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 mention of "good second issue" in prework issue template - design #5477

Closed
2 of 3 tasks
Tracked by #4432
roslynwythe opened this issue Sep 11, 2023 · 3 comments · Fixed by #5556
Closed
2 of 3 tasks
Tracked by #4432

replace mention of "good second issue" in prework issue template - design #5477

roslynwythe opened this issue Sep 11, 2023 · 3 comments · Fixed by #5556
Assignees
Labels
Complexity: Medium Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Sep 11, 2023

Overview

We need to replace mention of "good second issue" in the designer's prework issue template

Action Items

  • In your IDE open .github/ISSUE_TEMPLATE/pre-work-template---design.md
  • Replace
- Good first issue (one per person)
- Good second issue (one per person)

with

- Good first issue (two per person)
  • Refer to these instructions for testing and preparing the Pull Request.

Resources/Instructions

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 11, 2023
@github-actions
Copy link

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

@roslynwythe roslynwythe added Draft Issue is still in the process of being created Complexity: Small Take this type of issues after the successful merge of your second good first issue role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours Complexity: Medium Feature: Onboarding/Contributing.md Ready for Prioritization and removed Complexity: Small Take this type of issues after the successful merge of your second good first issue role missing size: missing Feature Missing This label means that the issue needs to be linked to a precise feature label. Draft Issue is still in the process of being created Complexity: Medium labels Sep 11, 2023
@roslynwythe roslynwythe added this to the 03.02 Onboarding flow milestone Sep 15, 2023
@roslynwythe roslynwythe removed Ready for Prioritization Complexity: Small Take this type of issues after the successful merge of your second good first issue labels Sep 15, 2023
@allison-truhlar allison-truhlar self-assigned this Sep 15, 2023
@github-actions
Copy link

Hi @allison-truhlar, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@allison-truhlar
Copy link
Member

Availability: M-F, 10-12pm ET
ETA: Monday 9/18 EOD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Projects
Development

Successfully merging a pull request may close this issue.

2 participants