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

Change QA Validation URL in add-github-handle issue template #6850

Closed
15 tasks done
tony1ee opened this issue May 11, 2024 · 6 comments · Fixed by #6999
Closed
15 tasks done

Change QA Validation URL in add-github-handle issue template #6850

tony1ee opened this issue May 11, 2024 · 6 comments · Fixed by #6999
Assignees
Labels
Complexity: Medium Feature: Administrative Administrative chores etc. role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@tony1ee
Copy link
Member

tony1ee commented May 11, 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 change the URL for QA validation in add-github-handle issue template so it defaults to code instead of preview.

Action Items

  • Open the file .github/ISSUE_TEMPLATE/add-github-handle.md in your code editor
  • Replace
For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/[INSERT-PATH-TO-PROJECT-FILE]  

with

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/_projects/[INSERT_PROJECT_FILE]?plain=1
  • 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 as [URL OF ISSUE TEMPLATE] and save for later use.

  • Verify the changes 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: [URL OF ISSUE TEMPLATE]
  • Replace the text in the square brackets (as well as the square brackets) with the URL of the updated issue template
  • 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

Resources/Instructions

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/.github/ISSUE_TEMPLATE/add-github-handle.md?plain=1
This issue is made for ER #6771.

@tony1ee tony1ee added Feature: Administrative Administrative chores etc. role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Medium size: 1pt Can be done in 4-6 hours ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels May 11, 2024
@Kle012 Kle012 self-assigned this May 14, 2024
Copy link

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

@Kle012
Copy link
Member

Kle012 commented May 14, 2024

i. Availability: 05/15/2024 3PM-5PM
ii. ETA: within 2 weeks

@tony1ee

This comment was marked as outdated.

@Kle012 Kle012 removed their assignment May 14, 2024
@Kle012

This comment was marked as outdated.

@tony1ee tony1ee added the ready for dev lead Issues that tech leads or merge team members need to follow up on label May 28, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the 08. Team workflow milestone Jun 2, 2024
@ExperimentsInHonesty ExperimentsInHonesty removed ready for dev lead Issues that tech leads or merge team members need to follow up on ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels Jun 11, 2024
@ino-iosdev ino-iosdev self-assigned this Jun 12, 2024
Copy link

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

@ino-iosdev
Copy link
Member

ino-iosdev commented Jun 12, 2024

ETA: EoD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Medium Feature: Administrative Administrative chores etc. role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Development

Successfully merging a pull request may close this issue.

4 participants