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.

Sign up for GitHub

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

Jump to bottom

ER: Changes Needed for add-github-handle issue template and Epic instruction comments #6771

Open
2 of 5 tasks
tony1ee opened this issue Apr 27, 2024 · 18 comments
Open
2 of 5 tasks

ER: Changes Needed for add-github-handle issue template and Epic instruction comments #6771

tony1ee opened this issue Apr 27, 2024 · 18 comments
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours Status: Updated No blockers and update is ready for review
Projects
Project Board
Milestone
08. Team workflow

Comments

@tony1ee
Copy link
Member

tony1ee commented Apr 27, 2024 •
edited

Emergent Requirement - Problem

we have decided to change the QA validation link in the add-github-handle issue template so it defaults to code instead of preview.

Details

Line planned to update in issue template

website/.github/ISSUE_TEMPLATE/add-github-handle.md

Line 38 in caa4f1b

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/[INSERT-PATH-TO-PROJECT-FILE]

we want to change it to

For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/_projects/[INSERT_PROJECT_FILE]?plain=1

Issue you discovered this emergent requirement in

Date discovered

04/25/2024

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@tony1ee
@roslynwythe

What happens if this is not addressed

If we don't make these changes, future issue makers for add-github-handle issues would create new issues that have irrelevant resource link and receive inaccurate instruction on how to populate placeholder in that link.

Resources

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

Creat an issue to change add-github-handle issue template .github/ISSUE_TEMPLATE/add-github-handle.md.
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
@tony1ee tony1ee added role: back end/devOps Tasks for back-end developers P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) ready for dev lead Issues that tech leads or merge team members need to follow up on size: 0.25pt Can be done in 0.5 to 1.5 hours Issue Making: Level 2 Make issue(s) from an ER or Epic ER Emergent Request labels Apr 27, 2024
@HackforLABot HackforLABot added this to New Issue Approval in Project Board Apr 27, 2024
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee added Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level and removed Complexity: Missing labels Apr 27, 2024
@tony1ee tony1ee mentioned this issue Apr 27, 2024
Closed
11 tasks
@tony1ee tony1ee changed the title ER: Changes Needed for add-github-handle issue template and ER: Changes Needed for add-github-handle issue template and Epic instruction comments Apr 27, 2024
@tony1ee tony1ee moved this from New Issue Approval to Emergent Requests in Project Board Apr 27, 2024
@roslynwythe

This comment was marked as outdated.

Sign in to view
@tony1ee

This comment was marked as outdated.

Sign in to view
@roslynwythe

This comment was marked as outdated.

Sign in to view
@tony1ee

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee self-assigned this Apr 28, 2024
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@tony1ee

This comment was marked as outdated.

Sign in to view
@ExperimentsInHonesty ExperimentsInHonesty added the Complexity: Small Take this type of issues after the successful merge of your second good first issue label Apr 30, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee removed their assignment Apr 30, 2024
@tony1ee

This comment was marked as outdated.

Sign in to view
@roslynwythe

This comment was marked as outdated.

Sign in to view
@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels May 3, 2024
@ExperimentsInHonesty ExperimentsInHonesty mentioned this issue May 3, 2024
Open
2 tasks
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on Added to dev/pm agenda and removed Ready for Prioritization labels May 3, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

Sign in to view
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@ExperimentsInHonesty

This comment was marked as outdated.

Sign in to view
@tony1ee

This comment was marked as outdated.

Sign in to view
@roslynwythe roslynwythe assigned tony1ee and unassigned roslynwythe May 11, 2024
@roslynwythe roslynwythe removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label May 11, 2024
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee moved this from Emergent Requests to In progress (actively working) in Project Board May 11, 2024
@tony1ee

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee mentioned this issue May 11, 2024
Open
15 tasks
@github-actions github-actions bot added the To Update ! No update has been provided label May 24, 2024
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee moved this from In progress (actively working) to Questions / In Review in Project Board May 24, 2024
@tony1ee

This comment was marked as outdated.

Sign in to view
@tony1ee tony1ee added Status: Updated No blockers and update is ready for review and removed To Update ! No update has been provided labels May 24, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Questions / In Review to ERs and epics that are ready to be turned into issues in Project Board Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue ER Emergent Request Issue Making: Level 2 Make issue(s) from an ER or Epic P-Feature: Project Info and Page A project's detail page (e.g. https://www.hackforla.org/projects/100-automations) role: back end/devOps Tasks for back-end developers size: 0.25pt Can be done in 0.5 to 1.5 hours Status: Updated No blockers and update is ready for review
Projects
Project Board
  
ERs and epics that are ready to be tu...
Milestone
08. Team workflow
Development

No branches or pull requests
3 participants
@roslynwythe @tony1ee @ExperimentsInHonesty