Edit complexity of tools to technology issue template
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github
- Domain
- tooling
Research direction
Open .github/ISSUE_TEMPLATE/project-tool-to-technology.md and inspect its front matter. Follow the linked Testing issue templates instructions in issue #4786, include the relevant URL in the pull request, and confirm the template uses the requested complexity label while preserving the other labels.
Written by the indexing model from the issue text.
Description
Prerequisites
- 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 and attend an onboarding session.
- You have already read our How to Contribute to Hack for LA Guide.
Overview
We need to revise the 'Project Profile Move Tool to Technology' template so that it uses the 'Complexity: Small' label instead of 'good first issue' to more accurately describe the complexity of issues created with this template
Action Items
- Open the file
.github/ISSUE_TEMPLATE/project-tool-to-technology.mdin your IDE - In the file front matter, replace the following:
labels: 'good first issue, P-Feature: Project Info and Page, P-Feature: Projects page, role: back end/devOps,
role: front end, size: 0.25pt, time sensitive'
with
labels: 'Complexity: Small, P-Feature: Project Info and Page, P-Feature: Projects page, role: back end/devOps,
role: front end, size: 0.25pt, time sensitive'
- Follow the instructions for Testing issue templates and include the relevant URL in your PR
Instructions for Merge Team
- After this issue is closed, mark #8750 'ready for prioritization' and remove the 'Dependency' label
Resources/Instructions
- Dominant language
- JavaScript
- Stars
- 364
- Forks
- 873
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 12
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: Small Feature: Infrastructure Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Complexity: See issue making label ER Feature: Infrastructure Issue Making: Level 2 non-PR contribution ready for merge team role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
good first issue P-Feature: Project Info and Page role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
All issues in hackforla/website
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·