Resolve codeql 6053

[junadkat32]

Fixes #6053

What changes did you make?

Replaced <a href='{{ leader.links.linkedin }}' target='_blank' title='Linkedin Profile'>

with

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

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

To resolve codeql alert 6053

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

No visual changes

[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 junadkat32-resolve-codeql-6053 gh-pages
git pull https://github.com/junadkat32/website.git resolve-codeql-6053

---

Note that CONTRIBUTING.md cannot previewed locally; rather it should be previewed at this URL:

https://github.com/junadkat32/website/blob/resolve-codeql-6053/CONTRIBUTING.md  

[Thinking-Panda]

Availability: Weekdays
Review ETA:2/13/24

[Thinking-Panda]

@junadkat32 , Thank you for working on this issue. Merge branches are setup correctly. The action item in the issue mentions to add the rel= attribute only for the LinkedIn Profile on line 54. Please reverse changes made to line 58. There will probably be another issue to make that change. Thanks!

[junadkat32]

@Thinking-Panda Yes, you are right. There is a separate issue for line 58and it was me who took up that issue and the PR has been approved. Please advise on further steps.

Thank you.

[Thinking-Panda]

@Thinking-Panda Yes, you are right. There is a separate issue for line 58and it was me who took up that issue and the PR has been approved. Please advise on further steps.

Thank you.

@junadkat32 , developers are expected to work on only one issue at a time and wait until the previous issue is merged to pick another issue. We need to check with the merge-team on further steps.

[roslynwythe]

@junadkat32 This PR will be closed, because you are assigned to a different open issue.

[junadkat32]

Hello @roslynwythe my previous PR was merged and I have reopened this PR.

[t-will-gillis]

Hey @junadkat32 - Closing this PR for a couple of reasons: first is that although you were previously, you are not currently assigned to this issue which is required for opening the PR. The other reason is that you have already completed 3 good first issues and, as is noted on the "Pre-work Checklist", you should be advancing to a Complexity: Small issue. Thanks!