-
-
Notifications
You must be signed in to change notification settings - Fork 766
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
ER: Changes Needed for add-github-handle issue template and Epic instruction comments #6771
Open
2 of 5 tasks
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
Milestone
Comments
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
This comment was marked as outdated.
This comment was marked as outdated.
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
Closed
11 tasks
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
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
ExperimentsInHonesty
added
the
Complexity: Small
Take this type of issues after the successful merge of your second good first issue
label
Apr 30, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
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
2 tasks
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
Ready for Prioritization
labels
May 3, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
removed
the
ready for dev lead
Issues that tech leads or merge team members need to follow up on
label
May 11, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
15 tasks
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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 ofpreview
.Details
Line planned to update in issue template
website/.github/ISSUE_TEMPLATE/add-github-handle.md
Line 38 in caa4f1b
we want to change it to
Issue you discovered this emergent requirement in
Date discovered
04/25/2024
Did you have to do something temporarily
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
Potential solutions [draft]
Creat an issue to change
add-github-handle
issue template .github/ISSUE_TEMPLATE/add-github-handle.md.Replace:
with:
The text was updated successfully, but these errors were encountered: