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

Replace Github with GitHub in _projects/tech-work-experience.md #7414

Closed
7 tasks done
daras-cu opened this issue Sep 9, 2024 · 9 comments · Fixed by #7589
Closed
7 tasks done

Replace Github with GitHub in _projects/tech-work-experience.md #7414

daras-cu opened this issue Sep 9, 2024 · 9 comments · Fixed by #7589
Assignees
Labels
Complexity: Medium P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@daras-cu
Copy link
Member

daras-cu commented Sep 9, 2024

Overview

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

Details

The instance of "Github" that you are changing seems to relate to the creation of this button on the https://www.hackforla.org/communities-of-practice page

that is created by https://github.com/hackforla/website/blob/gh-pages/pages/communities-of-practice.html.

Action Items

  • Open _projects/tech-work-experience.md in your IDE
  • Change
  - name: Github

to

  - name: GitHub
  • 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.
  • 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

Merge Team

@daras-cu daras-cu added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Medium P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) size: 1pt Can be done in 4-6 hours labels Sep 9, 2024
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: HfLA Website: Project Board Sep 9, 2024
@daras-cu daras-cu added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Sep 9, 2024
@t-will-gillis t-will-gillis added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Sep 9, 2024
@Priyanshu-2005
Copy link

hey @daras-cu I would like to work on this issue kindly assign me this issue.

@daras-cu
Copy link
Member Author

Hi @Priyanshu-2005, please see my response to your other comment on this issue:

@HackforLABot

This comment has been minimized.

@pluto-bell
Copy link
Member

pluto-bell commented Sep 16, 2024

Availability typically: Mon-Fri, 10 am - 5pm. I'll be traveling from Sept. 16th - Sept. 29th which will change this.

I'm beginning a bit of work on this today, and then will most likely have time again at the end of my travels.

@jphamtv jphamtv moved this from Prioritized backlog to In progress (actively working) in P: HfLA Website: Project Board Sep 20, 2024
@jphamtv
Copy link
Member

jphamtv commented Sep 20, 2024

Hi @pluto-bell I updated the status of this issue to 'In progress (actively working)'. Please remember to change the status after self-assigning issues from the Prioritized backlog. Thanks!

@HackforLABot HackforLABot added the To Update ! No update has been provided label Sep 27, 2024
@HackforLABot

This comment has been minimized.

@HackforLABot HackforLABot removed the To Update ! No update has been provided label Oct 4, 2024
@HackforLABot
Copy link
Contributor

@pluto-bell

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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 Tuesday, October 1, 2024 at 12:04 AM PST.

@HackforLABot HackforLABot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Oct 4, 2024
@HackforLABot
Copy link
Contributor

@pluto-bell

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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 Tuesday, October 8, 2024 at 12:05 AM PST.

@pluto-bell pluto-bell added Status: Updated No blockers and update is ready for review and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Oct 13, 2024
@pluto-bell
Copy link
Member

Working on issue this week
Available: 10 am - 5pm on weekdays

@HackforLABot HackforLABot removed the Status: Updated No blockers and update is ready for review label Oct 18, 2024
@github-project-automation github-project-automation bot moved this from In progress (actively working) to QA in P: HfLA Website: Project Board Oct 19, 2024
@kgold2018 kgold2018 moved this from QA to Done in P: HfLA Website: Project Board Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Projects
Development

Successfully merging a pull request may close this issue.

7 participants