Skip to content

Epic: Create Issues to Correctly Capitalize "Slack" in CONTRIBUTING.MD #6844

@tony1ee

Description

@tony1ee

Dependency

Overview

We need to create issues to correctly capitalize "Slack" in CONTRIBUTING.MD when it means when it's used to refer to the app or the company.

Details

We need to fix the following instances:

  • **If you have any other questions about your contributing process, feel free to reach out to the team in the [#hfla-site](https://hackforla.slack.com/archives/C4UM52W93) slack channel.**
  • Also, please let the tech leadership team 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.
  • - If you still do not see your changes after trying these steps, please feel free to reach out to the team in the [#hfla-site](https://hackforla.slack.com/archives/C4UM52W93) slack channel, or bring up your issue in a dev meeting.

Action Items

For each item in Details above, perform the following actions:

  • Create an issue using Blank Issue Template, or by clicking here
  • Change the Title to Fix Capitalization of "Slack" in CONTRIBUTING.MD
  • Replace the description with the following:
### 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](https://www.hackforla.org/getting-started).
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](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).
   
### 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.
[INSERT_LINE_PERMALINK]

### Action Items
- [ ] Open the file `CONTRIBUTING.MD` in your code editor
- [ ] On Line [INSERT_LINE_NUMBER], replace every `slack` with `Slack` **when it's used to refer to the app and the company**, **do not make changes within URLs**.
- [ ] Changes to CONTRIBUTING.md should not be tested locally, rather they need to 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]
```

### For Merge Team
- [ ] Release the dependency for this issue in #6844. If all the dependencies have been completed, close that issue.

### Resources/Instructions
- [Getting started with writing and formatting on GitHub](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)
- For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.MD?plain=1

This issue is part of Issue Making Issue #6844 and ER #6163.
  • in Overview, replace [INSERT_LINE_PERMALINK] with permalink of line of code
  • in Action Items, replace [INSERT_LINE_NUMBER] with actual line number
  • Remove all existing labels, and apply the following labels: Complexity: Small, Feature: Onboarding/Contributing.md, role: front end, size: 0.5pt, ready for merge team
  • submit new issue
  • add the newly created issue to Issues Created list in issue Epic: Create Issues to Correctly Capitalize "Slack" in CONTRIBUTING.MD #6844

Issues Created

Resources/Instructions

This Issue Making Issue is part of ER #6163

Metadata

Metadata

Assignees

Labels

Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelComplexity: SmallTake this type of issues after the successful merge of your second good first issueDependencyAn issue is blocking the completion or starting of another issueFeature: Onboarding/Contributing.mdIssue Making: Level 1Make issues from a template and a spreadsheetepicrole: front endTasks for front end developerssize: 0.5ptCan be done in 3 hours or less

Type

No type

Projects

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions