Header is missing a link to GitHub

[hendrikebbers]

🆕🐥 First Timers Only

This issue is reserved for people who have never contributed to Hiero or any open source project in general.
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues labeled by 'Good First Issue' is to help you make your first contribution to Hiero.

👾 Description of the issue

We should add a link to GitHub to the header of the page. It should link to https://github.com/LFDT-Hiero and shown as the github logo (https://fontawesome.com/icons/github?f=brands&s=solid). It should be shown at the end of the header with some gap to the regular menu items.

📋 Step by step guide to do a contribution

If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow. More information and concrete samples for shell commands for each step can be found in our CONTRIBUTING.md file.
A more detailed general documentation of the GitHub PR workflow can be found here.

• Claim this issue: Comment below that you are interested in working on the issue
• Wait for assignment: A community member with the given rights will add you as an assignee of the issue
• Fork the repository: You can do that in GitHub (by simply clicking the 'fork' button).
• Check out the forked repository
• Create a feature branch for the issue. We do not have a hard naming definition for branches but it is best practice to prefix the branch name with the issue id.
• Solve the issue in your branch.
• Commit your changes: Here, it is needed to add sign-off information to the commit to accept the "Developer Certificate of Origin" (https://developercertificate.org). More details can be found in our CONTRIBUTING.md
• Start a Pull Request (PR): We have a pattern for naming pull requests that a GitHub Action checks. We use that pattern to support the creation of automatic release notes.
• Check GitHub Actions: Several GitHub Actions will be triggered automatically for each PR. If a GitHub Action fails and you do not understand the cause of that error do not hesitate to add a comment to the PR and ask the Hiero developer community for support.
• Wait for reviews: Members of the Hiero developer community will review your PR. If a reviewer finds any missing pieces or a problem, he or she will start a discussion with you and describe the next steps for solving the problem.
• You did it 🎉: We will merge the fix in the develop branch. Thanks for being part of the Hiero community as an open-source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a chance to receive cool goodies like a T-Shirt. 🎽

🤔 Additional Information

If you have any questions, just ask us directly in this issue by adding a comment. You can join our community chat at Discord. A general manual about open-source contributions can be found here.

[23Jyoti]

Can you assign this work to me ?? I would like to work on the issue.

[Arnavpk]

I would like to do work on this issue and can make more good changes other than this issue too

[hendrikebbers]

I will assing @23Jyoti since he asked before @Arnavpk

[hendrikebbers]

@23Jyoti can you please confirm that you will work on the issue?

[23Jyoti]

@23Jyoti can you please confirm that you will work on the issue?

Yes I will

[rahul-chakradhari]

@hendrikebbers i wanna work on this sir
Its gonna two week she had'nt done yet i will do it

[abhirajadhikary06]

@hendrikebbers Sir,
this will be my very first contribution to Heiro, so may I take up this issue ?