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

[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 following line of code to correctly capitalize "Slack" when it's used to refer to the app or the company in our code and content. https://github.com/hackforla/website/blob/612389d3c6d6b6b86b179185096b489115cd55f2/.github/ISSUE_TEMPLATE/pre-work-template---design.md?plain=1#L66

Action Items

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

• [x] On Line 66, replace every slack with Slack when it's used to refer to the app and the company, do not make changes within URLs.

• [ ] 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

• [ ] 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.

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

  Screenshot of Repository Settings

  

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

  Screenshot of Default Branch Setting

  

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

  Screenshot of Issues Checkbox

  

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

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

• [ ] Verify the appearance of the issue template.

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

• [ ] 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]

• [ ] 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

• [ ] 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

• [ ] 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]

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

[gdkoo]

Availability: Mon-Thurs evenings after 7PM ETA: 8/25

[gdkoo]

Blocker: Noticing there's an additional uncapitalized slack in line 29: (through a slack message in the hfla-site channel) Should I go ahead and change this too?

[roslynwythe]

Blocker: Noticing there's an additional uncapitalized slack in line 29: (through a slack message in the hfla-site channel) Should I go ahead and change this too?

Hi @gdkoo thank you for mentioning that. We will include that in a new issue so no you won't need to update line 29.

[HackforLABot]

@gdkoo

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' 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 Tuesday, August 27, 2024 at 12:04 AM PST.}

[gdkoo]

Progress: Updated file, need to start pull request. Blockers: Resolved concern about updating additional uncapitalized slack. Availability: Weekday evenings ETA: 9/6