Update labels: Issue Template: alt-text-audit--dev

[cng008]

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

   Overview

   As developers, we need to add the labels from the Missing series so that we can avoid the GitHub bot taking off the labels when devs add them to issues.

   Action Items

   • [x] Navigate to .github/ISSUE_TEMPLATE/alt-text-audit--dev.md
   • [x] Replace the following line

     labels: 'Feature: Accessibility, good first issue, ready for dev lead, role: back end/devOps, role: front end, size: 1pt

     with

     labels: ['Feature: Accessibility', 'good first issue', 'ready for dev lead', 'role: back end/devOps', 'role: front end', 'size: 1pt', 'Complexity: Missing']

   • [x] Test the updated template using these instructions. Copy the contents of that comment into a new comment in this issue, and check off the boxes as you complete the steps.

For PR Reviewers and Merge Team To review this issue, click the link below under "Link for reviewers" and verify that the labels match the updated labels string in the issue.

Link for Reviewers This URL will be inserted by the dev during the test process and will be used by reviewers to preview the updated template. URL of the issue branch on the test Repository: [REPLACE THIS TEXT AND BRACKETS WITH THE URL]

For PM, Merge Team, or Tech Lead

• [ ] Once the pull request associated with this issue is approved and merged, please update and edit epic #4307 by
  • [ ] Checking off the dependency for this issue
  • [ ] If all dependencies are checked off, please move issue to the New Issue Approval column and remove the Dependency label

File and Code links you will need to work on this issue

• Directory to find the page in once you have it in your IDE: .github/ISSUE_TEMPLATE/alt-text-audit--dev.md
• This issue is part of epic #4307

[github-actions[bot]]

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

[roslynwythe]

Not sure why the bot moved this item to QA, so I'm moving it back to Prioritized Backlog.

[github-actions[bot]]

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

[Sk-223]

Instructions for testing updated issue templates:

• [x] Push your issue branch to your fork of the website repository, as described in [Section 3.1.a of CONTRIBUTING doc] https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#31a-push-all-changes-to-your-issue-branch, for example: git push --set-upstream origin test-update-labels-1234
• [x] The response from the push command will include the URL for creating a pull request. Copy/Paste the URL below for use after testing:
  https://github.com/hackforla/website/compare/gh-pages...Sk-223:website:update-labels-4477?expand=1
• [x] Browse to your fork of the website repository and click Settings
• [x] Change the default branch to the new issue branch
• [x] Further down on the settings page under Features, check the Issues checkbox
• [x] Browse to the Issues page, then click Labels
• [x] Create labels corresponding to each label that was listed in the updated issue template. The color of the labels don't have to match those on the hackforla/website repository, but the text of the labels must match exactly.
• [x] From the Issues page, click New Issue then locate the template updated by your issue, and click Get Started to open the issue template.
• [x] Copy/Paste the URL of the issue template into the Resources section of the issue, replacing the text: https://github.com/hackforla/website/pull/4844 This will enable others to check the template.
• [x] Verify the appearance of the issue template, including careful examination of the labels. If there is a discrepancy between the labels listed in the issue and the labels that appear on the issue template, ask a dev lead or merge team member for help.
• [x] Complete the PR process by visiting the URL saved from the push command
• [x] Copy these sections from the Issue into the PR
  • [x] "For PR Reviewers and Merge Team"
  • [x] "Link for Reviewers"
  • [x] "For PM, Merge Team, or Tech Lead"