Improvements to GHA 'Add Update' Label

[t-will-gillis]

Prerequisite

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.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As developers, we need to ensure that the GHA involving the To Update ! label creates clear comments and directions for the team to follow.

Action Items

• In the update-instructions-template.md file, add an additional sentence after '...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](https://github.com/hackforla/website/issues/1619#issuecomment-897315561) and [here](https://github.com/hackforla/website/issues/1908#issuecomment-877908152) are examples of well-formed questions.

• Testing GitHub Actions: After making the changes, confirm that the GitHub action works as intended. The hyperlinks for 'Here' and 'here' above may need to be edited.
• Merge Team and Leads: Release dependency on GitHub Actions: Automate In Progress Issue Updates: Hide Old Comments #1976 . May need to rewrite links that have expired since issue was written.

Note that you might want to do something outside the scope of the above pseudo-code. If so, be sure to leave comments in your PR or on this issue that justifies your reasoning. If you feel you need guidance, be sure to reach out! We cannot foresee whether this issue is solvable, or what hard decisions have to be made, but we would love to hear and help you!

Resources/Instructions

• schedule-fri-0700.yml
• add-label.js
• update-instructions-template.md

Never done GitHub actions? Start here!

Additional resources:

Events that trigger workflows
Workflow syntax for GitHub Actions
GitHub GraphQL

[github-actions]

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

[angieyan]

Availability: 8pm-9pm May 1; 10-11:30am May 2
ETA: EOD May 3, 23

[Hritik1503]

I am interested to work on this issue under Quine. So please assign me this task to me.

[angieyan]

@Hritik1503 you should assign yourself from the top right gear of assignees.