docs: flisk-sh/analytics has no issue templates or pull request template
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, yaml
- Domain
- documentation
Research direction
Start by looking at the repository's .github folder, which currently has neither an ISSUE_TEMPLATE directory nor a PULL_REQUEST_TEMPLATE.md. Add .github/ISSUE_TEMPLATE/bug_report.yml asking for the URL, steps to reproduce and expected result, plus a config.yml pointing questions at Discussions or the README, then add .github/PULL_REQUEST_TEMPLATE.md asking for a summary and the test command run. Follow the two RED/GREEN steps in the plan so each template has a checking test, and confirm the repo's Community Standards checklist shows both items as done with existing tests still passing.
Written by the indexing model from the issue text.
Description
Problem
flisk-sh/analytics has no issue templates and no pull request template. Bug reports arrive as free text without the URL, steps or expected result, and pull requests arrive without a test note or a summary of what changed.
Root Cause Analysis
The .github folder holds no ISSUE_TEMPLATE directory and no PULL_REQUEST_TEMPLATE.md. GitHub therefore shows a blank box for every new issue and pull request, and the Community Standards checklist shows these items as missing.
TDD Fix Plan
- RED: Add a check that .github/ISSUE_TEMPLATE has a bug form that asks for the URL, steps and expected result.
GREEN: Add bug_report.yml and a config.yml that points questions to Discussions or the README. - RED: Add a check that .github/PULL_REQUEST_TEMPLATE.md exists and asks for a summary and the test command run.
GREEN: Add the pull request template.
REFACTOR: Share one template set across org repos.
Acceptance Criteria
- New issue page offers a bug form
- New pull request is prefilled with the template
- Community Standards shows both items as done
- All new tests pass
- Existing tests still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 flisk-sh/analytics
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
All issues in flisk-sh/analytics
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·