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

Remove "good second issue" from CONTRIBUTING.md Section 2.3.b #5591

Closed
5 of 6 tasks
Tracked by #4506
roslynwythe opened this issue Sep 26, 2023 · 4 comments · Fixed by #5699
Closed
5 of 6 tasks
Tracked by #4506

Remove "good second issue" from CONTRIBUTING.md Section 2.3.b #5591

roslynwythe opened this issue Sep 26, 2023 · 4 comments · Fixed by #5699
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Wiki role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Sep 26, 2023

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
  2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to remove references to "good second issue" from CONTRIBUTING.md in order to avoid confusion, since we are no longer creating issues with the label `Complexity: good second issue'.

Action Items

  • In your local IDE, navigate to CONTRIBUTING.md and locate Section 2.3.b
  • Remove
* `Prioritized Backlog` column in the [filtered Project Board - **complexity: Good second issues** label](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22+label%3A%22complexity%3A+good+second+issue%22)
  • Do not make any changes outside the single instance above in Section 2.3.b
  • Changes to CONTRIBUTING.md cannot be tested locally, rather they must be tested after pushing the issue branch to your fork of the repository. Push your issue branch in the usual manner, but before creating the Pull Request, check your updates using this test URL. Also store the test URL for use in a later step:
https://github.com/[REPLACE WITH GITHUB HANDLE]/website/blob/[REPLACE WITH NAME OF ISSUE BRANCH]/CONTRIBUTING.md

(for example: https://github.com/bonniewolfe/website/blob/issue-branch-1234/CONTRIBUTING.md)

  • Create a pull request with your changes. In the Pull Request, after the "Why did you make the changes" section, add this line to help reviewers, replacing the text in brackets (and the brackets) with the test URL from the previous Action Item.
For Reviewers: Do not review locally, rather review changes at [REPLACE WITH TEST URL]

For Merge Team

Resources/Instructions

CONTRIBUTING.md
Getting started with writing and formatting on GitHub

@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 26, 2023
@github-actions

This comment was marked as outdated.

@roslynwythe roslynwythe added role: front end Tasks for front end developers Feature: Wiki Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less role: back end/devOps Tasks for back-end developers Ready for Prioritization and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Sep 26, 2023
Utkarsh3128 added a commit to Utkarsh3128/website that referenced this issue Sep 29, 2023
@anjolaaoluwa anjolaaoluwa added this to the 08. Team workflow milestone Oct 1, 2023
@segbuniwe segbuniwe self-assigned this Oct 4, 2023
@github-actions
Copy link

github-actions bot commented Oct 4, 2023

Hi @segbuniwe, 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 :)

@segbuniwe
Copy link
Member

Availability for this week: I will be available for ~6-10 hours this week to work on this issue.
My estimated ETA for completing this issue: I plan to complete this issue by Saturday, October 7.

@segbuniwe
Copy link
Member

ETA: I did not have the time that I originally thought I had, so I a will be completing this issue by Wednesday 10/11.

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 Feature: Wiki role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Projects
Development

Successfully merging a pull request may close this issue.

4 participants