From c292c4f26e55c624c72314aa65aaf29b716d1b71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9my=20Baudet?= Date: Tue, 29 Sep 2026 08:12:25 -0600 Subject: [PATCH 1/2] chore: add CODEOWNERS, dependabot, and community files Adds CODEOWNERS so the ruleset's code owner review requirement takes effect, a Dependabot config for GitHub Actions and the validator's pub dependencies, and the community files Wingspan ships: contributing guide, code of conduct, security policy, PR template, and issue templates. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017Vxxv9fVFGupLXEnmx5bSq --- .github/CODEOWNERS | 3 + .github/ISSUE_TEMPLATE/bug_report.yaml | 33 +++++ .github/ISSUE_TEMPLATE/chore.yaml | 28 ++++ .github/ISSUE_TEMPLATE/ci.yaml | 28 ++++ .github/ISSUE_TEMPLATE/config.yml | 1 + .github/ISSUE_TEMPLATE/documentation.yaml | 28 ++++ .github/ISSUE_TEMPLATE/feature_request.yaml | 28 ++++ .github/ISSUE_TEMPLATE/refactor.yaml | 28 ++++ .github/PULL_REQUEST_TEMPLATE.md | 16 +++ .github/dependabot.yaml | 16 +++ CODE_OF_CONDUCT.md | 76 +++++++++++ CONTRIBUTING.md | 142 ++++++++++++++++++++ SECURITY.md | 56 ++++++++ config/cspell.json | 2 + 14 files changed, 485 insertions(+) create mode 100644 .github/CODEOWNERS create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yaml create mode 100644 .github/ISSUE_TEMPLATE/chore.yaml create mode 100644 .github/ISSUE_TEMPLATE/ci.yaml create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/documentation.yaml create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yaml create mode 100644 .github/ISSUE_TEMPLATE/refactor.yaml create mode 100644 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 .github/dependabot.yaml create mode 100644 CODE_OF_CONDUCT.md create mode 100644 CONTRIBUTING.md create mode 100644 SECURITY.md diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS new file mode 100644 index 0000000..e990989 --- /dev/null +++ b/.github/CODEOWNERS @@ -0,0 +1,3 @@ +# Every request must be reviewed and accepted by: + +* @VeryGoodOpenSource/codeowners diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml new file mode 100644 index 0000000..8181178 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.yaml @@ -0,0 +1,33 @@ +name: Bug Report +description: Report a bug or unexpected behavior. +title: "fix: " +labels: ["bug"] +body: + - type: textarea + id: description + attributes: + label: Description + description: A clear description of the bug. + validations: + required: true + - type: textarea + id: steps-to-reproduce + attributes: + label: Steps to Reproduce + description: Steps to reproduce the behavior. + validations: + required: true + - type: textarea + id: expected-behavior + attributes: + label: Expected Behavior + description: What you expected to happen. + validations: + required: true + - type: textarea + id: additional-context + attributes: + label: Additional Context + description: Any other context about the problem. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/chore.yaml b/.github/ISSUE_TEMPLATE/chore.yaml new file mode 100644 index 0000000..47dc949 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/chore.yaml @@ -0,0 +1,28 @@ +name: Chore +description: Maintenance task, dependency update, or housekeeping. +title: "chore: " +labels: ["chore"] +body: + - type: textarea + id: description + attributes: + label: Description + description: A clear description of the chore. + validations: + required: true + - type: textarea + id: requirements + attributes: + label: Requirements + description: > + What must be true for this change to be complete? + Consider markdown lint, spell check, and structure validation. + validations: + required: false + - type: textarea + id: additional-context + attributes: + label: Additional Context + description: Any other context about the request. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/ci.yaml b/.github/ISSUE_TEMPLATE/ci.yaml new file mode 100644 index 0000000..25fd7b6 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/ci.yaml @@ -0,0 +1,28 @@ +name: CI +description: Suggest a CI/CD improvement. +title: "ci: " +labels: ["ci"] +body: + - type: textarea + id: description + attributes: + label: Description + description: A clear description of the CI change. + validations: + required: true + - type: textarea + id: requirements + attributes: + label: Requirements + description: > + What must be true for this change to be complete? + Consider markdown lint, spell check, and structure validation. + validations: + required: false + - type: textarea + id: additional-context + attributes: + label: Additional Context + description: Any other context about the request. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..3ba13e0 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1 @@ +blank_issues_enabled: false diff --git a/.github/ISSUE_TEMPLATE/documentation.yaml b/.github/ISSUE_TEMPLATE/documentation.yaml new file mode 100644 index 0000000..88578d5 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/documentation.yaml @@ -0,0 +1,28 @@ +name: Documentation +description: Suggest a documentation improvement. +title: "docs: " +labels: ["documentation"] +body: + - type: textarea + id: description + attributes: + label: Description + description: A clear description of the documentation change. + validations: + required: true + - type: textarea + id: requirements + attributes: + label: Requirements + description: > + What must be true for this change to be complete? + Consider markdown lint, spell check, and structure validation. + validations: + required: false + - type: textarea + id: additional-context + attributes: + label: Additional Context + description: Any other context about the request. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yaml new file mode 100644 index 0000000..4308f23 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.yaml @@ -0,0 +1,28 @@ +name: Feature Request +description: Suggest a new feature or enhancement. +title: "feat: " +labels: ["feature"] +body: + - type: textarea + id: description + attributes: + label: Description + description: A clear description of the feature. + validations: + required: true + - type: textarea + id: requirements + attributes: + label: Requirements + description: > + What must be true for this feature to be complete? + Consider markdown lint, spell check, and structure validation. + validations: + required: false + - type: textarea + id: additional-context + attributes: + label: Additional Context + description: Any other context about the request. + validations: + required: false diff --git a/.github/ISSUE_TEMPLATE/refactor.yaml b/.github/ISSUE_TEMPLATE/refactor.yaml new file mode 100644 index 0000000..82311c2 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/refactor.yaml @@ -0,0 +1,28 @@ +name: Refactor +description: Suggest a code change that neither fixes a bug nor adds a feature. +title: "refactor: " +labels: ["refactor"] +body: + - type: textarea + id: description + attributes: + label: Description + description: A clear description of what needs to be refactored and why. + validations: + required: true + - type: textarea + id: requirements + attributes: + label: Requirements + description: > + What must be true for this change to be complete? + Consider markdown lint, spell check, and structure validation. + validations: + required: false + - type: textarea + id: additional-context + attributes: + label: Additional Context + description: Any other context about the request. + validations: + required: false diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..5a9e04e --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,16 @@ + + +## Description + + + +## Type of Change + + + +- [ ] New feature (`feat`) +- [ ] Bug fix (`fix`) +- [ ] Code refactor (`refactor`) +- [ ] Documentation (`docs`) +- [ ] CI change (`ci`) +- [ ] Chore (`chore`) diff --git a/.github/dependabot.yaml b/.github/dependabot.yaml new file mode 100644 index 0000000..817edec --- /dev/null +++ b/.github/dependabot.yaml @@ -0,0 +1,16 @@ +version: 2 +updates: + - package-ecosystem: "github-actions" + directory: "/" + schedule: + interval: "daily" + labels: + - "dependencies" + - "no-auto-update" + - package-ecosystem: "pub" + directory: "/scripts" + schedule: + interval: "weekly" + labels: + - "dependencies" + - "no-auto-update" diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..3c9dffb --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,76 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, sex characteristics, gender identity and expression, +level of experience, education, socio-economic status, nationality, personal +appearance, race, religion, or sexual identity and orientation. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +- Using welcoming and inclusive language +- Being respectful of differing viewpoints and experiences +- Gracefully accepting constructive criticism +- Focusing on what is best for the community +- Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +- The use of sexualized language or imagery and unwelcome sexual attention or + advances +- Trolling, insulting/derogatory comments, and personal or political attacks +- Public or private harassment +- Publishing others' private information, such as a physical or electronic + address, without explicit permission +- Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or +reject comments, commits, code, wiki edits, issues, and other contributions +that are not aligned to this Code of Conduct, or to ban temporarily or +permanently any contributor for other behaviors that they deem inappropriate, +threatening, offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at . All +complaints will be reviewed and investigated and will result in a response that +is deemed necessary and appropriate to the circumstances. The project team is +obligated to maintain confidentiality with regard to the reporter of an incident. +Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see + diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..a6fcb65 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,142 @@ +# 🦄 Contributing to VGV FFCA Plugin + +First of all, thank you for taking the time to contribute! 🎉👍 Before you do, please carefully read this guide. + +## Getting Started + +1. **Fork** the repository and clone your fork locally. +2. Create a new branch from `main` for your work. +3. Install the [Dart SDK](https://dart.dev/get-dart) and `jq` if you plan to touch the hook or the validator. + +## Types of Contributions + +| Contribution | Where | +| ------------ | ----- | +| **New skill** | `skills//SKILL.md` | +| **Improve an existing skill** | Edit the relevant `skills/*/SKILL.md` | +| **Agent** | `agents/` directory | +| **Hook** | `hooks/` directory | +| **Validator rules** | `scripts/validate_layers.dart` and its tests in `scripts/test/` | +| **Bug reports and feature requests** | [GitHub Issues](https://github.com/VeryGoodOpenSource/vgv-ffca-plugin/issues) | + +## The FFCA Reference + +`references/ffca_architecture.md` mirrors the canonical FFCA documentation. It is the single source of truth for the conventions, and the skills point into it by section name instead of restating it. + +- Do not edit the reference to change a convention. Propose the change upstream, then sync the mirror. +- When a skill needs a convention, link to the relevant section of the reference. Do not copy the rule into the skill. + +## Adding a New Skill + +### 1. Create the skill file + +Create `skills//SKILL.md`. The file must begin with YAML frontmatter: + +```yaml +--- +name: +description: "What the skill covers, in one sentence." +when_to_use: Use when working in an FFCA monorepo and the user asks about X. +--- +``` + +| Field | Required | Rules | +| ----- | -------- | ----- | +| `name` | Yes | Lowercase letters, numbers, and hyphens only. Prefix FFCA skills with `ffca-` | +| `description` | Yes | What the skill covers | +| `when_to_use` | Yes | When the skill should trigger, scoped to FFCA repos so it does not fire in layered repos | +| `allowed-tools` | No | Tools the skill may use without a permission prompt | + +### 2. Update the README skills table + +Add a row to the skills table and the direct-invocation list in `README.md`. + +### 3. Update `plugin.json` keywords + +Add relevant keywords to the `keywords` array in `.claude-plugin/plugin.json` when the skill covers new ground. + +## Skill Writing Guidelines + +- **Use clear directives.** Say "Use X" or "Do not use Y", not "consider" or "prefer". +- **Fence all code blocks** with language identifiers, such as ` ```dart `. +- **Provide complete, copy-pasteable snippets**, not fragments. +- **Reference packages by full name**, such as `package:go_router`. +- **Show anti-patterns alongside correct patterns** when it helps readers see what to avoid. +- **Keep prose tight.** Every word in a SKILL.md consumes context the user needs for their actual work. Prefer decision tables to long if/else narratives, and keep to one sentence per rule. + +## Working on the Validator + +The validator lives in `scripts/` and imports only `dart:io`, so the hook runs with just the Dart SDK. The `pubspec.yaml` there exists only for the test suite. + +```bash +cd scripts +dart pub get +dart analyze --fatal-infos +dart format --output=none --set-exit-if-changed . +dart test +``` + +Add a fixture under `scripts/test/fixtures/` for every new rule, covering both a passing and a failing workspace. + +## Testing Locally + +From the repository root, launch Claude Code pointed at this directory: + +```bash +claude --plugin-dir . +``` + +`--plugin-dir` loads the plugin for that session only and overrides any marketplace-installed copy. + +| Component | How to verify | +| --------- | ------------- | +| **Skills** | Run `/help`. Skills appear namespaced as `/vgv-ffca-plugin:`. Invoke one to confirm it triggers. | +| **Agent** | Ask Claude to audit an FFCA repo and confirm it dispatches `ffca-layer-auditor`. | +| **Hook** | In an FFCA repo, have Claude add a forbidden dependency to a `pubspec.yaml` and confirm the edit is blocked. | + +Restart the session after editing a `SKILL.md`, `hooks/hooks.json`, or `.claude-plugin/plugin.json`. + +Before you push, run the same check CI runs: + +```bash +claude plugin validate . +``` + +## CI Checks + +Every pull request runs the following checks automatically: + +| Check | What it does | Config | +| ----- | ------------ | ------ | +| Markdown lint | Lints all `*.md` files | `config/custom.markdownlint.jsonc` | +| Spelling | Runs cspell on all `*.md` files | `config/cspell.json` | +| Layer validator | Analyzes, formats, and tests the Dart validator | `scripts/` | +| Skills lint | Validates every skill's frontmatter, structure, and links | VGV `skills_lint` reusable workflow | +| Plugin validation | Validates the plugin manifest via Claude Code CLI | `claude plugin validate .` | + +If the spelling check flags a legitimate word, add it to the `words` array in `config/cspell.json`. + +## Commit Convention + +Use [Conventional Commits](https://www.conventionalcommits.org/). PRs are squash-merged with the PR title as the commit message, so the **PR title** must follow the format, since release-please builds the changelog from it: + +```text +type(scope): description +``` + +| Type | When to use | Example | +| ---- | ----------- | ------- | +| `feat` | New skill or feature | `feat: add ffca-testing skill` | +| `fix` | Fix an error or incorrect guidance | `fix: correct $extra hydration example` | +| `docs` | Documentation-only change | `docs: clarify install steps` | +| `chore` | Maintenance and tooling | `chore: update cspell config` | +| `refactor` | Restructure without changing behavior | `refactor: split validator rules` | +| `ci` | CI pipeline changes | `ci: cache Dart dependencies` | + +## Pull Requests + +- Branch from `main`. +- Keep PRs focused, with one skill per PR for new skills. +- Fill out the [PR template](.github/PULL_REQUEST_TEMPLATE.md). +- Ensure all CI checks pass before requesting review. +- Link any related issues in the PR description. diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..0e541e9 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,56 @@ +# Security Policy + +## Supported Versions + +| Version | Supported | +| ------- | --------- | +| 0.1.x | Yes | + +Only the latest release on `main` receives security updates. + +## Reporting a Vulnerability + +### GitHub Private Vulnerability Reporting (preferred) + +Report vulnerabilities through [GitHub's private vulnerability reporting](https://github.com/VeryGoodOpenSource/vgv-ffca-plugin/security/advisories/new). + +### Email + +Send an email to `tools@verygood.ventures` with a `[SECURITY]` subject prefix. + +### What to Include + +- A description of the vulnerability +- Steps to reproduce the issue +- Affected files or components + +### Response Timeline + +- **Acknowledgment**: within 5 business days +- **Assessment**: within 10 business days +- **Notification**: you will be notified when a fix is released + +## Scope + +VGV FFCA Plugin is a Claude Code plugin. Its only executable code is the validation hook and the Dart validator it runs. The security-relevant surface areas are: + +### Skill, Agent, and Reference Files (`skills/*/`, `agents/`, `references/`) + +- Insecure code examples that developers may copy into production +- Outdated or misleading security guidance +- Recommendations that contradict current best practices + +### Hook and Validator (`hooks/*.sh`, `scripts/*.dart`) + +- Command injection through file paths or hook payloads +- Unsafe path handling or traversal outside the workspace +- Unintended code execution + +### Plugin Manifest and MCP Config (`.claude-plugin/plugin.json`, `.mcp.json`) + +- Excessive permissions +- Exploitable MCP server definitions + +## Recognition + +We are happy to acknowledge reporters in the fix PR upon request. diff --git a/config/cspell.json b/config/cspell.json index 4536f76..c9f9c27 100644 --- a/config/cspell.json +++ b/config/cspell.json @@ -3,9 +3,11 @@ "words": [ "dtos", "ffca", + "frontmatter", "mappr", "mocktail", "operationalizes", + "pasteable", "posthog", "pubspec", "pubspecs", From 5eef0c20311beecadf3279f2af9e28b6b09fbf96 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9my=20Baudet?= Date: Tue, 29 Sep 2026 08:16:04 -0600 Subject: [PATCH 2/2] chore: drop files already covered by #9 CODEOWNERS, the PR and issue templates, and the Dependabot config land in #9, so this PR keeps only the contributing guide, security policy, and code of conduct. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_017Vxxv9fVFGupLXEnmx5bSq --- .github/CODEOWNERS | 3 -- .github/ISSUE_TEMPLATE/bug_report.yaml | 33 --------------------- .github/ISSUE_TEMPLATE/chore.yaml | 28 ----------------- .github/ISSUE_TEMPLATE/ci.yaml | 28 ----------------- .github/ISSUE_TEMPLATE/config.yml | 1 - .github/ISSUE_TEMPLATE/documentation.yaml | 28 ----------------- .github/ISSUE_TEMPLATE/feature_request.yaml | 28 ----------------- .github/ISSUE_TEMPLATE/refactor.yaml | 28 ----------------- .github/PULL_REQUEST_TEMPLATE.md | 16 ---------- .github/dependabot.yaml | 16 ---------- 10 files changed, 209 deletions(-) delete mode 100644 .github/CODEOWNERS delete mode 100644 .github/ISSUE_TEMPLATE/bug_report.yaml delete mode 100644 .github/ISSUE_TEMPLATE/chore.yaml delete mode 100644 .github/ISSUE_TEMPLATE/ci.yaml delete mode 100644 .github/ISSUE_TEMPLATE/config.yml delete mode 100644 .github/ISSUE_TEMPLATE/documentation.yaml delete mode 100644 .github/ISSUE_TEMPLATE/feature_request.yaml delete mode 100644 .github/ISSUE_TEMPLATE/refactor.yaml delete mode 100644 .github/PULL_REQUEST_TEMPLATE.md delete mode 100644 .github/dependabot.yaml diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS deleted file mode 100644 index e990989..0000000 --- a/.github/CODEOWNERS +++ /dev/null @@ -1,3 +0,0 @@ -# Every request must be reviewed and accepted by: - -* @VeryGoodOpenSource/codeowners diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml deleted file mode 100644 index 8181178..0000000 --- a/.github/ISSUE_TEMPLATE/bug_report.yaml +++ /dev/null @@ -1,33 +0,0 @@ -name: Bug Report -description: Report a bug or unexpected behavior. -title: "fix: " -labels: ["bug"] -body: - - type: textarea - id: description - attributes: - label: Description - description: A clear description of the bug. - validations: - required: true - - type: textarea - id: steps-to-reproduce - attributes: - label: Steps to Reproduce - description: Steps to reproduce the behavior. - validations: - required: true - - type: textarea - id: expected-behavior - attributes: - label: Expected Behavior - description: What you expected to happen. - validations: - required: true - - type: textarea - id: additional-context - attributes: - label: Additional Context - description: Any other context about the problem. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/chore.yaml b/.github/ISSUE_TEMPLATE/chore.yaml deleted file mode 100644 index 47dc949..0000000 --- a/.github/ISSUE_TEMPLATE/chore.yaml +++ /dev/null @@ -1,28 +0,0 @@ -name: Chore -description: Maintenance task, dependency update, or housekeeping. -title: "chore: " -labels: ["chore"] -body: - - type: textarea - id: description - attributes: - label: Description - description: A clear description of the chore. - validations: - required: true - - type: textarea - id: requirements - attributes: - label: Requirements - description: > - What must be true for this change to be complete? - Consider markdown lint, spell check, and structure validation. - validations: - required: false - - type: textarea - id: additional-context - attributes: - label: Additional Context - description: Any other context about the request. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/ci.yaml b/.github/ISSUE_TEMPLATE/ci.yaml deleted file mode 100644 index 25fd7b6..0000000 --- a/.github/ISSUE_TEMPLATE/ci.yaml +++ /dev/null @@ -1,28 +0,0 @@ -name: CI -description: Suggest a CI/CD improvement. -title: "ci: " -labels: ["ci"] -body: - - type: textarea - id: description - attributes: - label: Description - description: A clear description of the CI change. - validations: - required: true - - type: textarea - id: requirements - attributes: - label: Requirements - description: > - What must be true for this change to be complete? - Consider markdown lint, spell check, and structure validation. - validations: - required: false - - type: textarea - id: additional-context - attributes: - label: Additional Context - description: Any other context about the request. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 3ba13e0..0000000 --- a/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1 +0,0 @@ -blank_issues_enabled: false diff --git a/.github/ISSUE_TEMPLATE/documentation.yaml b/.github/ISSUE_TEMPLATE/documentation.yaml deleted file mode 100644 index 88578d5..0000000 --- a/.github/ISSUE_TEMPLATE/documentation.yaml +++ /dev/null @@ -1,28 +0,0 @@ -name: Documentation -description: Suggest a documentation improvement. -title: "docs: " -labels: ["documentation"] -body: - - type: textarea - id: description - attributes: - label: Description - description: A clear description of the documentation change. - validations: - required: true - - type: textarea - id: requirements - attributes: - label: Requirements - description: > - What must be true for this change to be complete? - Consider markdown lint, spell check, and structure validation. - validations: - required: false - - type: textarea - id: additional-context - attributes: - label: Additional Context - description: Any other context about the request. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yaml deleted file mode 100644 index 4308f23..0000000 --- a/.github/ISSUE_TEMPLATE/feature_request.yaml +++ /dev/null @@ -1,28 +0,0 @@ -name: Feature Request -description: Suggest a new feature or enhancement. -title: "feat: " -labels: ["feature"] -body: - - type: textarea - id: description - attributes: - label: Description - description: A clear description of the feature. - validations: - required: true - - type: textarea - id: requirements - attributes: - label: Requirements - description: > - What must be true for this feature to be complete? - Consider markdown lint, spell check, and structure validation. - validations: - required: false - - type: textarea - id: additional-context - attributes: - label: Additional Context - description: Any other context about the request. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/refactor.yaml b/.github/ISSUE_TEMPLATE/refactor.yaml deleted file mode 100644 index 82311c2..0000000 --- a/.github/ISSUE_TEMPLATE/refactor.yaml +++ /dev/null @@ -1,28 +0,0 @@ -name: Refactor -description: Suggest a code change that neither fixes a bug nor adds a feature. -title: "refactor: " -labels: ["refactor"] -body: - - type: textarea - id: description - attributes: - label: Description - description: A clear description of what needs to be refactored and why. - validations: - required: true - - type: textarea - id: requirements - attributes: - label: Requirements - description: > - What must be true for this change to be complete? - Consider markdown lint, spell check, and structure validation. - validations: - required: false - - type: textarea - id: additional-context - attributes: - label: Additional Context - description: Any other context about the request. - validations: - required: false diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md deleted file mode 100644 index 5a9e04e..0000000 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ /dev/null @@ -1,16 +0,0 @@ - - -## Description - - - -## Type of Change - - - -- [ ] New feature (`feat`) -- [ ] Bug fix (`fix`) -- [ ] Code refactor (`refactor`) -- [ ] Documentation (`docs`) -- [ ] CI change (`ci`) -- [ ] Chore (`chore`) diff --git a/.github/dependabot.yaml b/.github/dependabot.yaml deleted file mode 100644 index 817edec..0000000 --- a/.github/dependabot.yaml +++ /dev/null @@ -1,16 +0,0 @@ -version: 2 -updates: - - package-ecosystem: "github-actions" - directory: "/" - schedule: - interval: "daily" - labels: - - "dependencies" - - "no-auto-update" - - package-ecosystem: "pub" - directory: "/scripts" - schedule: - interval: "weekly" - labels: - - "dependencies" - - "no-auto-update"