Updated pre-work-template---design.md labels

[LRenDO]

Fixes #4480

What changes did you make and why did you make them ?

• Updated labels in .github/ISSUE_TEMPLATE/pre-work-template---design.md
  from
  labels: 'Feature: Onboarding/Contributing.md, prework, role: design, size: 1pt'
  to
  labels: ['Feature: Onboarding/Contributing.md', 'prework', 'role: design', 'size: 1pt', 'Complexity: Missing']
• Verified labels appeared correctly in the pre-work design template
• Per the issue, this was done to avoid the GitHub bot taking off the labels when devs add them to issues.

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

Visuals before changes are applied

Visuals after changes are applied

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: Updated Pre-work Design Template

For PM, Merge Team, or Tech Lead

• See test instructions
• Once the pull request associated with this issue is approved and merged, please update and edit epic Creating issues to Add Missing Labels to Issue Templates #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

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

From your project repository, check out a new branch and test the changes.

git checkout -b LRenDO-update-pre-work-template-labels-4480 gh-pages
git pull https://github.com/LRenDO/website.git update-pre-work-template-labels-4480

[one2code]

ETA: 6/2/23
Availability 8-10PM EST, 6/2/23

[roslynwythe]

Hi @LRenDO thank you for working on this issue. It looks good so far. For the convenience of reviewers, please go to the issue and copy the section "Link for Reviewers" (along with the text/link) into this PR. Thank you !

[blulady]

Instructions for testing updated issue templates:

• 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 below for use after testing:
  [REPLACE THIS TEXT WITH URL FOR CREATING PR]
• Browse to your fork of the website repository and click Settings

Screenshot of Repository Settings

• Change the default branch to the new issue branch

Screenshot of Default Branch Setting

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

Screenshot of Issues Checkbox

• Browse to the Issues page, then click Labels

Screenshot - creating labels in the test Repo

• 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.
• 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/Paste the URL of the issue template into the Resources section of the issue, replacing the text: [REPLACE THIS TEXT WITH URL OF THE ISSUE TEMPLATE ON THE TEST REPO]
  This will enable others to check the template.
• Verify that the labels listed in the issue all appear on the issue template. 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.
• If the labels listed in the issue match those listed on the issue template, complete the PR process by visiting the URL saved from the push command
• Copy these sections from the Issue into the PR
  • "For PR Reviewers and Merge Team"
  • "Link for Reviewers"
  • "For PM, Merge Team, or Tech Lead"

[LRenDO]

Hi @LRenDO thank you for working on this issue. It looks good so far. For the convenience of reviewers, please go to the issue and copy the section "Link for Reviewers" (along with the text/link) into this PR. Thank you !

Hi @roslynwythe! Whoops, looks like I was moving too quickly and didn't get the whole section when I copied. Should be fixed now. Thanks for catching that!

[one2code]

I've verified that the changes requested in issue #4767 have been correctly implemented in the .github/ISSUE_TEMPLATE/pre-work-template---design.md file. After following the testing instructions provided by @roslynwythe and @blulady, I was able to successfully add and implement the labels on the pre-work template --design when creating a new issue.

I'm very impressed by the your attention to detail in your PR report. You took the time and effort to clearly state where file changes where taking place, and what file changes were being made. Furthermore, you quickly made requested changes to make the testing process easier. Excellent work!

[roslynwythe]

Thank you @LRenDO for great work on this issue. Your code change is correct and clean, you completed the test procedure and displayed the test template URL, and created a well-formed Pull Request which describes your work.