Add new variable github-handle for member Muhi-Dean Othman in 100-automations.md

[roslynwythe]

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

• [x] Open the file _projects/100-automations.md in the IDE
• [x] Replace:

- name: Muhi-Dean Othman

with

- name: Muhi-Dean Othman
  github-handle: 

• [x] Do not use a tab to indent "github-handle". YAML doesn't allow tabs; it requires spaces.
• [x] 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.

Merge Team

• [ ] Release the dependency of this issue in #5441
• [ ] After the last dependency has been released, close #5441

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/100-automations.md Webpage: https://www.hackforla.org/projects/100-automations

• This issue is part of #5441

[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

NOTE: Please ignore the adding proper labels 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

[abhayguptas]

Hey @roslynwythe, Hope you are doing well. My self Abhay, I'm ready to solve this asap. I am ready to push changes and open PR. Please assign it to me. Thanks !

[ExperimentsInHonesty]

@professorabhay. Thanks for your interest.

Prerequisite for working on this issue

1. 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 and attend an onboarding session.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

[github-actions[bot]]

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

[sornekian]

Availability: Weeknights 7-11pm ETA: 12/26/23 8pm

[github-actions[bot]]

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

[ExperimentsInHonesty]

@samuelusc I am moving this issue to the in progress column, since you are working on it. On future issues please move the issue after you self assign.

[samuelusc]

@roslynwythe Thank you. I will do that next time.

[samuelusc]

i. Availability: I am going to work with it during the week. ii. ETA: Expect that it can be done by next Thursday or Sunday.

[github-actions[bot]]

@samuelusc

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' 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 Monday, March 4, 2024 at 11:06 PM PST.}

[samuelusc]

1. Progress: has created pull request and waitting for PR review.
2. Blockers: Waitting for PR review
3. Availability: 20 hours
4. ETA: After the pr review