Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
13 of 16 tasks
roslynwythe opened this issue Aug 5, 2024 · 11 comments · Fixed by #7514
Closed
13 of 16 tasks
Assignees

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Aug 5, 2024

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.

- Lastly, you can post your question in the hfla slack channel and link the issue you're working on, so other volunteers can see and respond

Action Items

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

  • 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

    image

  • Change the default branch to the new issue branch

    Screenshot of Default Branch Setting

    image

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

    Screenshot of Issues Checkbox

    image

  • 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

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

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Aug 5, 2024
@github-project-automation github-project-automation bot moved this to New Issue Approval in P: HfLA Website: Project Board Aug 5, 2024

This comment has been minimized.

@roslynwythe roslynwythe added Complexity: Medium size: 1pt Can be done in 4-6 hours role: back end/devOps Tasks for back-end developers Feature: Onboarding/Contributing.md and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Aug 5, 2024
@roslynwythe roslynwythe added this to the 08. Team workflow milestone Aug 5, 2024
@gdkoo gdkoo self-assigned this Aug 15, 2024
@HackforLABot

This comment has been minimized.

@gdkoo gdkoo moved this from Prioritized backlog to In progress (actively working) in P: HfLA Website: Project Board Aug 15, 2024
@gdkoo

This comment was marked as outdated.

@gdkoo

This comment was marked as outdated.

@roslynwythe roslynwythe changed the title Fix Capitalization of "Slack" in Issue Template pre-work-template---design.md Fix Capitalization of "Slack" in Issue Template pre-work-template---design.md line 66 Aug 19, 2024
@roslynwythe

This comment was marked as outdated.

@HackforLABot HackforLABot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Aug 30, 2024
@HackforLABot

This comment has been minimized.

@gdkoo

This comment was marked as outdated.

@gdkoo gdkoo removed the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Aug 30, 2024
@gdkoo gdkoo added the Status: Updated No blockers and update is ready for review label Aug 30, 2024
@HackforLABot HackforLABot removed the Status: Updated No blockers and update is ready for review label Sep 6, 2024
@HackforLABot HackforLABot added the To Update ! No update has been provided label Sep 13, 2024
@HackforLABot

This comment was marked as outdated.

@gdkoo

This comment was marked as outdated.

@gdkoo gdkoo moved this from In progress (actively working) to New Issue Approval in P: HfLA Website: Project Board Sep 18, 2024
@gdkoo gdkoo removed the To Update ! No update has been provided label Sep 18, 2024
@gdkoo gdkoo removed their assignment Sep 18, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Make Issues: ERs and epics in P: HfLA Website: Project Board Sep 23, 2024
@jchue jchue self-assigned this Sep 23, 2024
@HackforLABot
Copy link
Contributor

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

@jchue
Copy link
Member

jchue commented Sep 23, 2024

  • Availability: M-F, after 5 PM PDT
  • ETA: EOD tomorrow, 9/24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
5 participants