dkritarth / dkritarth/FreeFlow
No .github community health files (issue/PR templates, CONTRIBUTING)
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
No \`.github/\` directory at all — no issue templates, no PR template, no \`CONTRIBUTING.md\`, no \`CODE_OF_CONDUCT.md\`, no \`FUNDING.yml\`.
For a repo being promoted for wider visibility, this matters: GitHub surfaces "Community Standards" completeness in the Insights tab, and contributors bounce off repos with no PR template / contribution guide.
**Ask:**
- \`.github/ISSUE_TEMPLATE/bug_report.md\` and \`feature_request.md\` (or a \`config.yml\` + forms)
- \`.github/PULL_REQUEST_TEMPLATE.md\`
- \`CONTRIBUTING.md\` — how to run the Worker locally (\`npm run worker:dev\`), how to test the CLI, coding conventions (there currently are none documented — see standards findings on PR #3)
- Optional: \`CODE_OF_CONDUCT.md\` if aiming for outside contributors
Contributor guide
No contributing guide indexed for this repository
Research direction
Create the requested .github/ISSUE_TEMPLATE/bug_report.md, feature_request.md, and PULL_REQUEST_TEMPLATE.md files, plus CONTRIBUTING.md. Start by checking the existing npm run worker:dev command and the CLI testing workflow; document local Worker setup, CLI testing, and conventions. Done means the community files exist and contributors can follow the guide, with CODE_OF_CONDUCT.md left as an optional separate addition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100