mirror of
https://github.com/Egonex-AI/Understand-Anything.git
synced 2026-06-22 10:58:03 +08:00
Tirth Kanani
aef940fcde
Closes a cluster of community-profile gaps (#248, #249, #251, #252) in one PR rather than four micro-PRs that all touch the same surface area. ### Templates (#251, #252) - .github/ISSUE_TEMPLATE/bug_report.yml — required fields for repro (plugin version, platform, OS, project language, file count); the four pieces of context that are missing from ~every current bug report. - .github/ISSUE_TEMPLATE/feature_request.yml — leads with the *problem* rather than the proposed solution, which keeps maintainer review focused on whether to solve, not just how. - .github/ISSUE_TEMPLATE/question.yml — separate from bug to keep the bug queue triagable. - .github/ISSUE_TEMPLATE/config.yml — disables blank issues and routes general discussion to README + Discussions. - .github/PULL_REQUEST_TEMPLATE.md — includes the version-bump checklist that CLAUDE.md says must stay in sync across 5 manifests; otherwise every contributor learns this rule by getting their PR bounced. ### Community files - CODE_OF_CONDUCT.md — short, project-specific document that names the expectations and reporting path. Not a verbatim Contributor Covenant to keep it readable. - SECURITY.md — describes the project's local-only threat model explicitly so reporters know what's in / out of scope before they spend time on a writeup. Points at GitHub private vulnerability reporting as the primary channel. ### CI (#249) - ci.yml now also runs on pushes to main, not only PRs. Without this, a direct push to main (which happens when maintainers merge a PR branch locally) doesn't trigger CI, so a regression can land green- looking and stay broken for days. - Added a concurrency group that cancels stale runs for the same ref. Saves runner minutes and keeps the per-ref status meaningful. - Used `github.ref` (a controlled value), not user-controlled input, so no script-injection surface. ### package.json (#248) - Added description, license, repository, bugs, homepage, keywords — the standard set for npm package discoverability and so GitHub's community-profile check shows the project at 100%.
27 lines
793 B
Markdown
27 lines
793 B
Markdown
## Summary
|
|
|
|
<!-- One or two sentences on what this PR changes and why. -->
|
|
|
|
## Linked issue(s)
|
|
|
|
<!-- e.g. Closes #123, Refs #456. Leave empty if there's no tracking issue. -->
|
|
|
|
## How I tested this
|
|
|
|
<!-- Concrete steps. "Ran the test suite" is fine; "Ran /understand on a 3k-file
|
|
Swift repo and verified the dashboard shows non-empty edges" is better. -->
|
|
|
|
- [ ] `pnpm lint`
|
|
- [ ] `pnpm --filter @understand-anything/core test`
|
|
- [ ] `pnpm test`
|
|
- [ ] Manual smoke test (describe above)
|
|
|
|
## Versioning
|
|
|
|
<!-- If this PR ships a user-visible behavior change, bump the version in ALL
|
|
five manifests per CLAUDE.md. If it's docs/tests/internal-only, leave them
|
|
alone and the maintainer will bump on merge. -->
|
|
|
|
- [ ] Version bumped in all five manifests, OR
|
|
- [ ] N/A — internal/docs-only change
|