Create Issue Template for Updates to CONTRIBUTING.md

[roslynwythe]

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

We need to create a GitHub issue template for updates to CONTRIBUTING.md so that issues can be created efficiently and so that we can provide developers with special instructions for previewing changes to CONTRIBUTING.md.

Action Items

• Create a new file .github/ISSUE_TEMPLATE/update-CONTRIBUTING.md with YAML frontmatter:

---
name: update CONTRIBUTING.md
about: 'For making updates to CONTRIBUTING.md'
title: 'Update CONTRIBUTING.md Section [INSERT SECTION #]'
labels: 'Feature: Wiki, Complexity: Small, role: back
  end/devOps, role: front end, size: 0.5pt'
assignees: ''

---

• The body of the issues should come from this template
• Refer to these instructions for testing and preparing the Pull Request.

Resources/Instructions

Manually creating a single issue template for your repository

• This issue is part of Epic: Create issues to add github-handle to leadership teams #5441

[roslynwythe]

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

[INSERT BRIEF DESCRIPTION OF THE UPDATE]

Action Items

• In your local IDE, navigate to CONTRIBUTING.md
• Replace

[INSERT LINE OF CURRENT CODE HERE]

with

[INSERT DESIRED LINE OF CODE HERE]

• With CONTRIBUTING.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 CONTRIBUTING.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]/CONTRIBUTING.md

(for example: https://github.com/bonniewolfe/website/blob/issue-branch-1234/CONTRIBUTING.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

CONTRIBUTING.md
Getting started with writing and formatting on GitHub

[github-actions]

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

[erinzz]

Availability: M-F 9-5
ETA: 9/21 EOD