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

gha labels test 33 #1119

Open
2 tasks
t-will-gillis opened this issue Nov 4, 2024 · 1 comment
Open
2 tasks

gha labels test 33 #1119

t-will-gillis opened this issue Nov 4, 2024 · 1 comment

Comments

@t-will-gillis
Copy link
Owner

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.
  2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

Our website needs to be free of misspellings so that our reputation for quality is maintained. In this issue a misspelling in the [REPLACE WITH WHERE] on the [REPLACE WITH NAME OF PAGE] page will be corrected.

Action Items

  • For the file [REPLACE WITH DIRECTORY & NAME OF FILE (e.g., /pages/communities-of-practice.html)], correct the spelling from "[REPLACE WITH MISSPELLED WORD]" to "[REPLACE WITH CORRECT SPELLED WORD]", so
    [REPLACE WITH CURRENT CODE]
    
    becomes
    [REPLACE WITH FUTURE CODE - WHAT IT WILL LOOK LIKE AFTER ITS FIXED]
    
  • Use Docker to test changes locally, in both desktop and mobile views

Resources

Website page with issue: [REPLACE WITH URL OF PAGE ON WEBSITE]
File on GitHub: https://github.com/hackforla/website/blob/gh-pages/REPLACE WITH DIRECTORY & NAME OF FILE (e.g., /pages/communities-of-practice.html)]

Copy link

github-actions bot commented Nov 4, 2024

Hi @t-will-gillis.

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

  • Feature

NOTE: Please ignore this 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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Approval
Development

No branches or pull requests

1 participant