Fix Capitalization of "Slack" in Issue Template pre-work-template---design.md line 29

[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.
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 fix the template to correctly capitalize "Slack" when it's used to refer to the app or the company in our code and content.

Action Items

• [x] Open the file /.github/ISSUE_TEMPLATE/pre-work-template---design.md in your code editor

• [x] In the following line replace every slack with Slack (This is line 29 at the time this issue was written but may have a different line number due to recent updates)

  - [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Wednesdays and Sundays). In case, you are unable in any given week, you should reach out to the design lead. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the design lead know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.

• [x] when it's used to refer to the app and the company, do not make changes within URLs.

• [x] Push your issue branch to your fork of the website repository, as described in Section 3.1.a of CONTRIBUTING doc, for example: git push --set-upstream origin test-update-labels-1234

• [x] The response from the push command will include the URL for creating a pull request. Copy/Paste the URL for creating the Pull Request for later.

• [x] Browse to your fork of the website repository and click Settings

  Screenshot of Repository Settings

  

• [x] Change the default branch to the new issue branch

  Screenshot of Default Branch Setting

  

• [x] Further down on the settings page under Features, check the Issues checkbox

  Screenshot of Issues Checkbox

  

• [x] From the Issues page, click "New Issue" then locate the template updated by your issue, and click "Get Started" to open the issue template.

• [x] Copy the URL of the issue creation page and save for later use.

• [x] Verify the appearance of the issue template.

• [x] Complete the Pull Request process by visiting the URL saved from the push command.

• [x] In the PR copy/paste this text immediately before the section "Screenshots of Proposed Changes Of The Website"

  
  ### For Reviewers

• Use this URL to check the updated issue template: [INSERT URL of issue creation page]

• [x] Replace the text in the square brackets (as well as the square brackets) with the URL of the updated issue template in your fork of the repository

• [x] Submit your pull request with your changes for review

• [ ] After PR is merged, be sure to follow the steps above to change your default branch back to gh-pages and to disable Issues feature

For Merge Team

• [x] Release the dependency for this issue in #6842. If all the dependencies have been completed, close that issue.

Resources/Instructions

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/.github/ISSUE_TEMPLATE/pre-work-template---design.md?plain=1

• This issue is part of Issue Making Issue #6842 and ER #6163.

[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, Size

NOTE: Please ignore this 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

[HackforLABot]

Hello @maadeshsivakumar, we appreciate you taking on this issue, however it looks like you're already working on another issue at this time. Please wait until your current issue is merged before taking on another issue. :)

We are going to unassign you from this issue so you can focus on your current issue.

Hfla appreciates you! :)

[HackforLABot]

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

[vanessasinam]

Availability: Mon-Fri 12pm - 4pm EST ETA: 09/04/2024

[vanessasinam]

Status: Completed.