Update Pre-Work Checklist (Dev) with Section 1.7

[danvgar]

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 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.

Overview

The Pre-Work Checklist is used to properly onboard new members with the Hack for LA process. At the moment thePre-Work Checklist - Dev only lists completing steps 1.1-1.6 of CONTRIBUTING.md. It should be amended to list completing steps 1.1-1.7 of CONTRIBUTING.md

Action Items

• [ ] In your local IDE, navigate to .github/ISSUE_TEMPLATE/pre-work-template--dev.md
• [ ] Replace

- [ ] Complete steps 1.1 - 1.6 in [Part 1: Setting up the development environment within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-1-setting-up-the-development-environment)

with

- [ ] Complete steps 1.1 - 1.7 in [Part 1: Setting up the development environment within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-1-setting-up-the-development-environment)

• [ ] With pre-work-template--dev.md still open, make a note of the section in which the replaced content appears, so that you will know where to look in the document to preview the change.
• [ ] Changes to pre-work-template--dev.md cannot be tested locally, rather they must be tested after pushing the issue branch to your fork of the repository. Push your issue branch in the usual manner, but before creating the Pull Request, check your updates using this test URL. Also store the test URL for use in a later step:

https://github.com/[REPLACE WITH GITHUB HANDLE]/website/blob/[REPLACE WITH NAME OF ISSUE BRANCH]/.github/ISSUE_TEMPLATE/pre-work-template--dev.md

(for example: https://github.com/bonniewolfe/website/blob/issue-branch-1234/.github/ISSUE_TEMPLATE/pre-work-template--dev.md)

• [ ] Create a pull request with your changes. In the Pull Request, after the "Why did you make the changes" section, add this line to help reviewers, replacing the text in brackets (and the brackets) with the test URL from the previous Action Item.

For Reviewers: Do not review changes locally, rather, review changes at [REPLACE WITH TEST URL]

Resources/Instructions

• Pre-Work Checklist - Dev
• Getting started with writing and formatting on GitHub
• This issue is part of #6041

[github-actions[bot]]

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

[danvgar]

Hi @lukewangm , this issue is still awaiting approval and isn't ready to be worked on. Please only pick up issues within the Prioritized Backlog column! Thank you! :)

[github-actions[bot]]

Hi @ExperimentsInHonesty, 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]

• This has been integrated into the issue that was already started: https://github.com/hackforla/website/issues/4944#issuecomment-2144457123

I am prioritizing this issue, only if issue https://github.com/hackforla/website/issues/4944 has not been finished.

[github-actions[bot]]

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

[elisetvy]

Availability: today 6/5 ETA: EOD