Resolve CodeQL alert 18 "Potentially unsafe external link"

[roslynwythe]

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 alert "Potentially unsafe external link" which appears in the CodeQL alert 18 by adding the attribute rel="noopener noreferrer"

Action Items

• The following item is required for GitHub to establish tracking between this issue and the alert. No action is required. You may simply check the checkbox. 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/INSERT-ALERT-ID
• Open the file pages/communities-of-practice.html in your IDE
• Replace

<a href='{{ leader.links.github }}' target='_blank' title='GitHub Profile'>

with

<a href='{{ leader.links.github }}' target='_blank' title='GitHub Profile' rel="noopener noreferrer">

• 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/communities-of-practice
3. This issue is part of Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

[github-actions]

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

[samuelusc]

i. Availability: I will be working with the issue this week and next week.
ii. ETA: Expect that it can be done before next Thursday or Sunday meeting.

[github-actions]

@samuelusc

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 PM PST.}

[samuelusc]

Progress: has created pull request and waitting for PR review.
Blockers: Waitting for PR review
Availability: 20 hours(next week)
ETA: After the pr review
Pictures (optional): if need, I can upload the updated code screenshot