Updated pr instructions demo

[roslynwythe]

Fixes #4

What changes did you make?

-

-

Why did you make the changes (we will use this info to test)?

-

-

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


Additional Action Items for Pull Request authors:

• [ ] After creating a Pull Request, wait for the GitHub checks to complete, then check for errors/warnings displayed in the GitHub check results and in GitHub bot comments.
  • [ ] If warnings are displayed, they must be addressed prior to pull request review.
    • [ ] DO NOT DISMISS any alerts or warnings. Alerts should be dismissed by merge team/dev leads after review.
    • [ ] If this is a good first issue, apply the label linter warning. Merge team/dev leads will provide assistance.
    • [ ] If this is not a good first issue, follow the instructions below that apply to the specific type of warning detected:
      If CodeQL annotations/warnings are displayed:

      Read the alert details then determine if the alert is a false positive or if code changes should be made to resolve the alert.

      If you determine that the alert is a false positive, describe your reasoning below in the section "What changes did you make in response to linter recommendations?". The alert will be dismissed by a member of the merge/dev lead team following the review of this issue.

      If code changes are required to resolve the alert, the changes will be considered within the scope of the issue. Make the changes and describe them below in the section "What changes did you make in response to linter recommendations?"

      If you are unsure how to manage the warning, submit an issue using this template
      If spell checker "unknown word" messages are displayed locally or in GitHub check results:

      if there was an actual misspelling, make the spelling correction. Confirm that the spell check message is resolved. Note the correction in the section "What changes did you make in response to code linter recommendations?" below.

      if the "unknown word" should be considerd a "word" (ie "hackforla"), edit the file `cspell.json` and add the term to the "words" array then confirm that the spell checker message is resolved. Note that change in the section "What changes did you make in response to code linter recommendations?" below.

      if the "unknown word" should be ignored by the spell checker (such as the name of an individual) edit the file `cspell.json` and add the term to the "ignoreWords" array. Confirm that the spell checker message is resolved. Note that change in the section "What changes did you make in response to code linter recommendations?" below.

      if you are unsure how to manage the warning, or if multiple warnings are displayed and you propose that an entire section (or the entire page) should be excluded from spell checking, submit an issue using this template

What changes did you make in response to linter recommendations?

-

-

[roslynwythe]

Fixes #replace_this_text_with_the_issue_number

What changes did you make?

Why did you make the changes (we will use this info to test)?

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

Additional Action Items for PR authors:

• [ ] After creating a Pull Request, wait for the GitHub checks to complete, then check for errors/warnings displayed in the GitHub check results and in GitHub bot comments.

  • [ ] If no warnings are displayed, your pull request is ready for review.

  • [ ] If warnings are displayed, DO NOT DISMISS any alerts or warnings. Follow these steps to make your PR ready for review:

  • [ ] If this is a good first issue, just apply the label linter warning.

  • [ ] If this is not a good first issue, follow the instructions below that apply to the specific type of warning detected:

If CodeQL annotations/warnings are displayed: If spell checker messages are displayed locally or in GitHub check results:

What changes did you make in response to linter recommendations?