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 label in add-github-handle.md #7600

Closed
15 tasks done
ExperimentsInHonesty opened this issue Oct 20, 2024 · 4 comments · Fixed by #7656
Closed
15 tasks done

Replace label in add-github-handle.md #7600

ExperimentsInHonesty opened this issue Oct 20, 2024 · 4 comments · Fixed by #7656
Assignees
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly ready for product role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Oct 20, 2024

Overview

We need to change the ready for label on the add-github-handle.md issue template so that the merge team can handle more of the issue reviews.

Action Items

  • Open the files /.github/ISSUE_TEMPLATE/add-github-handle.md
  • In the following text, replace ready for dev lead label with ready for merge team label
labels: 'Complexity: Small, feature: spelling, good first issue, P-Feature: Project
  Info and Page, ready for dev lead, role: back end/devOps, role: front end, size:
  0.5pt, size: 0.25pt'
  • Push your issue branch to your fork of the website repository, as described in Section 3.1.a of CONTRIBUTING doc, for example: git push --set-upstream origin test-update-labels-1234

  • The response from the push command will include the URL for creating a pull request. Copy/Paste the URL for creating the Pull Request for later.

  • Browse to your fork of the website repository and click Settings

    Screenshot of Repository Settings

    image

  • Change the default branch to the new issue branch

    Screenshot of Default Branch Setting

    image

  • Further down on the settings page under Features, check the Issues checkbox

    Screenshot of Issues Checkbox

    image

  • From the Issues page, click "New Issue" then locate the template updated by your issue, and click "Get Started" to open the issue template.

  • Copy the URL of the issue creation page and save for later use.

  • Verify the appearance of the issue template.

  • Complete the Pull Request process by visiting the URL saved from the push command.

  • In the PR copy/paste this text immediately before the section "Screenshots of Proposed Changes Of The Website"

 ### For Reviewers
- Use this URL to check the updated issue template: [INSERT URL of issue creation page]
  • Replace the text in the square brackets (as well as the square brackets) with the URL of the updated issue template in your fork of the repository
  • Submit your pull request with your changes for review
  • After PR is merged, be sure to follow the steps above to change your default branch back to gh-pages and to disable Issues feature

Resources/Instructions

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/.github/ISSUE_TEMPLATE/add-github-handle.md?plain=1

@ExperimentsInHonesty ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Draft Issue is still in the process of being created label Oct 20, 2024
@HackforLABot HackforLABot removed the Draft Issue is still in the process of being created label Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty self-assigned this Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Draft Issue is still in the process of being created role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly size: 1pt Can be done in 4-6 hours and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing Complexity: Missing size: missing labels Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title Replace ready for dev lead with ready for merge label in some of our issue templates Replace ready for dev lead with ready for merge label in add-github-handle.md Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title Replace ready for dev lead with ready for merge label in add-github-handle.md Replace label in add-github-handle.md Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty added Ready for Prioritization and removed role: front end Tasks for front end developers Draft Issue is still in the process of being created labels Oct 20, 2024
@ExperimentsInHonesty ExperimentsInHonesty removed their assignment Oct 20, 2024
@siyunfeng siyunfeng self-assigned this Oct 24, 2024
@HackforLABot
Copy link
Contributor

Hello @siyunfeng, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

@HackforLABot HackforLABot moved this from Prioritized backlog to New Issue Approval in P: HfLA Website: Project Board Oct 24, 2024
@siyunfeng siyunfeng moved this from New Issue Approval to In progress (actively working) in P: HfLA Website: Project Board Oct 24, 2024
@siyunfeng siyunfeng moved this from In progress (actively working) to Prioritized backlog in P: HfLA Website: Project Board Oct 24, 2024
@siyunfeng siyunfeng self-assigned this Oct 28, 2024
@siyunfeng siyunfeng moved this from Prioritized backlog to In progress (actively working) in P: HfLA Website: Project Board Oct 28, 2024
@HackforLABot
Copy link
Contributor

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

@siyunfeng
Copy link
Member

Availability: Weekdays (6-10 PM, EDT)
ETA: Thursday 10/31/2024

@siyunfeng
Copy link
Member

Hi, @ExperimentsInHonesty !

I want to clarify what do I need to do with Verify the appearance of the issue template.?

Does it mean manually editing and adding all the labels from the updated file /.github/ISSUE_TEMPLATE/add-github-handle.md to the issue template? Because I don't see those labels in the URL I provided to the reviewers in my PR. The only label shown in the issue template I created is good first issue.

  • Original issue template:

labels-section-in-the-original-issue-template

  • New issue template:

labels-section-in-the-new-issue-template

@siyunfeng siyunfeng moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Board Oct 29, 2024
@siyunfeng siyunfeng added Status: Help Wanted Internal assistance is required to make progress and removed Status: Help Wanted Internal assistance is required to make progress labels Oct 31, 2024
@github-project-automation github-project-automation bot moved this from Questions / In Review to QA in P: HfLA Website: Project Board Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly ready for product role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours
Projects
3 participants