Replace `Github` with `GitHub` in _data/internal/communities/project-management.yml

[roslynwythe]

Overview

We need to replace Github with GitHub so that we display the company name correctly, and we need to test the changes to ensure the behavior and appearance of any and all related webpages are unchanged.

Action Items

• [x] Open _data/internal/communities/project-management.yml in your IDE
• [x] Change

  - name: Github

  to

  - name: GitHub

• [x] Find all the files that are connected to this change. (e.g., if its a yml or md file, what files or scripts use the data stored in that file). And document briefly how they work together.
• [x] Define where you expect the change to show up on the website (e.g., the footer of the website). Can be on multiple pages
• [ ] Write a test procedure, in a comment, and then use it to test the change. Include a link to this comment in your PR.
• [ ] Add/commit changes then create a PR as usual. Document the test procedure in the Pull Request.

Resources

• website/_data/internal/communities/project-management.yml
• This issue resulted from #6161

Merge Team

• [x] After closing this issue, check off the dependency in #6161. If all dependecies have been completed, close #6161

[github-actions[bot]]

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

[HackforLABot]

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

[buneeIsSlo]

edited ETA because I'm caught up with something else

Availability: 7am to 11am on weekdays ETA: before 23-JUL-24 e.o.d