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 spell-check-audit.md #7601

Closed
15 tasks done
Tracked by #7602
ExperimentsInHonesty opened this issue Oct 20, 2024 · 2 comments · Fixed by #7713
Closed
15 tasks done
Tracked by #7602

Replace label in spell-check-audit.md #7601

ExperimentsInHonesty opened this issue Oct 20, 2024 · 2 comments · Fixed by #7713
Assignees
Labels
Complexity: Medium Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly 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 spell-check-audit.md so that the merge team can handle more of the issue reviews.

Action Items

  • Open the files /.github/ISSUE_TEMPLATE/spell-check-audit.md
  • In the following text items, replace ready for dev lead label with ready for merge team label
labels: 'Complexity: Small, feature: spelling, ready for dev lead, role: back end/devOps,
  role: front end, size: 0.5pt'
 - [ ] Move this issue to the Questions/In Review column and apply the label `ready for dev lead` 
  • 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/spell-check-audit.md?plain=1

@HackforLABot
Copy link
Contributor

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

@aswutmaxcy
Copy link
Member

i. Availability: 5am - 2pm (PST) M-F
ii. ETA: EoD tomorrow (11/08/24)

@aswutmaxcy aswutmaxcy moved this from In progress (actively working) to Questions / In Review in P: HfLA Website: Project Board Nov 9, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Questions / In Review to In progress (actively working) in P: HfLA Website: Project Board Nov 13, 2024
@github-project-automation github-project-automation bot moved this from In progress (actively working) to QA in P: HfLA Website: Project Board Nov 18, 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 role: back end/devOps Tasks for back-end developers size: 1pt Can be done in 4-6 hours
Projects
Development

Successfully merging a pull request may close this issue.

3 participants