mirror of
https://github.com/Luchexx/wacrm.git
synced 2026-11-02 09:19:51 +00:00
3799c224d8
Nine paperwork files + one devDep. All support work for a repo that's about to be public; zero runtime behaviour change. - CONTRIBUTING.md at root. Dev loop, script reference, PR style, code style, review process. Short on prose, long on specifics. - .github/CODE_OF_CONDUCT.md adopts Contributor Covenant 2.1 by reference (no inlined text). Points reports to the maintainer's email and GitHub's private flow. - .github/ISSUE_TEMPLATE/ — structured YAML forms for bug and feature reports, plus config.yml that disables blank issues and surfaces the security-disclosure + docs links. The bug form asks for version, runtime, and logs up front so triage doesn't start with a round of "where is it running?". - .github/pull_request_template.md — short checklist; nudges toward typecheck / lint / build before submit without being long enough to skip. - .github/dependabot.yml — weekly npm + github-actions scans, grouped so Supabase / @types / dev-only patches batch into single PRs instead of six per week. Next / React / Tailwind / eslint- config-next are ignored so majors stay manual. - .editorconfig — LF, UTF-8, 2 spaces, final newline, strip trailing whitespace (except in Markdown where trailing spaces are line breaks). - .prettierrc — single quotes + trailing-comma es5, matches the plurality quote style in the codebase (336 single vs 236 double in imports). Tailwind plugin sorts class names. - .prettierignore — node_modules, build output, lockfile, migrations. - package.json adds "format" / "format:check" scripts and pins prettier + prettier-plugin-tailwindcss as devDeps. - package-lock.json refreshed for the new devDeps. Important: existing source files are NOT reformatted in this PR. 153 files would change if we ran `npm run format`, which would balloon the diff and make review impossible. The reformat pass is a separate, deliberate PR. Typecheck clean; `npx prettier --check` on the new config files passes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
53 lines
1.6 KiB
YAML
53 lines
1.6 KiB
YAML
name: Feature request
|
|
description: Propose a new feature or a meaningful enhancement.
|
|
title: "[feat] "
|
|
labels: ["enhancement", "triage"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the idea. Features with a clear user story and a couple
|
|
of alternatives considered tend to move the fastest.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: What's the problem?
|
|
description: What are you trying to do today that WaCRM makes harder than it should?
|
|
placeholder: |
|
|
When a broadcast ends I have no way to see which recipients
|
|
didn't reply so I can follow up manually.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: What would you like to see?
|
|
description: Describe the feature from the user's perspective, not the implementation.
|
|
placeholder: |
|
|
On the broadcast detail page, a "No reply" filter that lists
|
|
recipients who received but didn't reply within 24 hours.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives you considered
|
|
description: Things that kinda work today, workarounds, related features in other tools.
|
|
validations:
|
|
required: false
|
|
|
|
- type: dropdown
|
|
id: scope
|
|
attributes:
|
|
label: Scope
|
|
description: Your guess — we'll re-scope if needed.
|
|
options:
|
|
- Small (a couple of hours)
|
|
- Medium (a couple of days)
|
|
- Large (a couple of weeks, probably breaks into multiple PRs)
|
|
validations:
|
|
required: false
|