Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed GitHub spelling in files #6447

Closed
wants to merge 2 commits into from

Conversation

SteeRevo
Copy link
Member

Fixes #6161

What changes did you make?

  • Edited the spelling of Github, github to the proper spelling of GitHub

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

  • GitHub is a company name and should only be github when in a url, variable or directory name

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

Visuals before changes are applied

ems_triage_tracker

tech_work_experience

tookit

Visuals after changes are applied

ems_triage_tracker_fixed

tech_work_experience_fixed

tookit_fixed

Other changes were made to comments that cannot be seen on the website

@github-actions github-actions bot added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Medium P-Feature: Toolkit https://www.hackforla.org/toolkit/ P-Feature: Getting Started https://www.hackforla.org/getting-started P-Feature: Navigation P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.25pt Can be done in 0.5 to 1.5 hours Issue Making: Level 2 Make issue(s) from an ER or Epic Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request labels Mar 11, 2024
Copy link

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 SteeRevo-change-github-name-6161 gh-pages
git pull https://github.com/SteeRevo/website.git change-github-name-6161

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

https://github.com/SteeRevo/website/blob/change-github-name-6161/CONTRIBUTING.md  

@t-will-gillis
Copy link
Member

Hey @SteeRevo - I think there has been a misunderstanding. Unless @ExperimentsInHonesty or @roslynwythe has told you something different (and let me know if that is the case), ERs are not issues to work directly off of. Of course, it would be very easy to do a search/replace all instances of 'GitHub' text using VSCode, but that is not the reason for these issues. An ER like #6161 is an "issue to make more issues", hence the Issue Making label. Bonnie is pointing out the numerous locations where the GItHub reference 'might', 'can', or 'must' be changed so that someone writes an epic of 15 or 20 good first issues or possibly Complexity: Small issues.

Again, if you were specifically told something different, please let me know.

Having said that, if you would like to work on writing a group of issues from this one, let us know and we would be happy to help you (and thrilled to have more people writing issues). Otherwise, if you are looking for a Complexity: Medium issue to work on, please select one that is in the "Prioritized Backlog" column.

Closing this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level ER Emergent Request good first issue Good for newcomers Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Communities of Practice https://www.hackforla.org/communities-of-practice P-Feature: Getting Started https://www.hackforla.org/getting-started P-Feature: Navigation P-Feature: Toolkit https://www.hackforla.org/toolkit/ ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ER: Find all the places that GitHub should be GitHub and fix
2 participants