Resolve CodeQL alert 22 and 24 "Potentially unsafe external link"

[roslynwythe]

Dependency

• pages/guides.html is published

Note: when the above dependency is satisfied, before prioritizing this issue we must reopen the CodeQL alert on this page: https://github.com/hackforla/website/security/code-scanning/22 and https://github.com/hackforla/website/security/code-scanning/24

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. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to resolve the "Potentially unsafe external link" alerts which appears in the CodeQL alert 22 and alert 24 by adding the attribute rel="noopener noreferrer"

Action Items

• The following items are required for GitHub to establish tracking between this issue and the alerts. No action is required. You may simply check the checkboxes. If you do follow the link to learn more about CodeQL alerts, DO NOT DISMISS THE ALERT.
  • https://github.com/hackforla/website/security/code-scanning/22
  • https://github.com/hackforla/website/security/code-scanning/24
• Open the file pages/guides.html in your IDE
• Replace BOTH instances of

          <a href="{{ item.links.linked-in }}" target="_blank" title="Linkedin Profile" class="fa fa-linkedin fa-xl" style="margin-right: 13px;
          text-decoration: none;"></a>

with

          <a href="{{ item.links.linked-in }}" target="_blank" title="Linkedin Profile" class="fa fa-linkedin fa-xl" style="margin-right: 13px;
          text-decoration: none;" rel="noopener noreferrer"></a>

• Using Docker, check the page remains the same in mobile, tablet, and desktop views as on the current website (See 2 in the Resources/Instructions section below)

Merge Team

• When this issue is completed, check off the issue in Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

Resources/Instructions

1. GitHub CodeQL documentation
2. webpage: https://www.hackforla.org/guides
3. This issue is part of Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

[github-actions]

Hi @roslynwythe.

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

• Complexity, Role, Feature, Size

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:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[github-actions]

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

[t-will-gillis]

OK to close: Both issues marked as "Fixed" by Dependabot:
https://github.com/hackforla/website/security/code-scanning/22
https://github.com/hackforla/website/security/code-scanning/24

• Note: occurred after PR Update codeql.yml to automatically create new CodeQL issues #6503 merged

[kgold2018]

CodeQL determined that the alerts attached to the PRs were automatically "fixed" after merging:

• Update codeql.yml to automatically create new CodeQL issues #6503