Add github-handle for Kate Rose in hellogov.md
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Edit _projects/hellogov.md and use the project.md file template to confirm the YAML field and indentation. Run the Docker-based site check, inspect the Hellogov project page at all screen sizes, and compare it with the linked QA view; done means the github-handle field is present and the page appearance is unchanged.
Written by the indexing model from the issue text.
Description
Prerequisite
- Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started Page.
- Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.
Overview
We need to create a single variable github-handle to hold the github handle for each member of the leadership team. Eventually github-handle will replace the github and picture variables, reducing redundancy in the project file.
Action Items
- Open the file
_projects/hellogov.mdin the IDE - Replace:
- name: Kate Rose
with
- name: Kate Rose
github-handle:
- Do not use a tab to indent
github-handle. YAML doesn't allow tabs; it requires spaces. - Using docker, confirm that the appearance of the project webpage is unchanged at all screen sizes. The project webpage URL can be found below under Resources.
For Merge Team
- Release the dependency for this issue in #5441. If all the dependencies have been completed, close that issue.
Resources/Instructions
https://github.com/hackforla/website/wiki/project.md-file-template
https://jekyllrb.com/
For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/_projects/hellogov.md?plain=1
Project Webpage: https://www.hackforla.org/projects/hellogov
- This issue is part of #5441.
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 873
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: Small Feature: Infrastructure Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Complexity: Medium Feature: Administrative ready for merge team role: back end/devOps role: front end size: 0.5pt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Complexity: See issue making label ER Feature: Infrastructure Issue Making: Level 2 non-PR contribution ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
All issues in hackforla/website
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
light
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aemdemos/patients-stryker#253 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·