diff --git a/.github/dependabot.yml b/.github/dependabot.yml new file mode 100644 index 00000000..0586bf0e --- /dev/null +++ b/.github/dependabot.yml @@ -0,0 +1,24 @@ +# Keep dependency update scheduling centralized in this repository configuration. +version: 2 +updates: + - package-ecosystem: github-actions + directory: / + schedule: + interval: weekly + commit-message: + prefix: ci(deps) + + - package-ecosystem: npm + directory: / + schedule: + interval: weekly + commit-message: + prefix: chore(deps) + include: scope + + - package-ecosystem: pip + directory: / + schedule: + interval: weekly + commit-message: + prefix: chore(deps) diff --git a/.github/scripts/check_issue_readiness.py b/.github/scripts/check_issue_readiness.py new file mode 100644 index 00000000..1707254b --- /dev/null +++ b/.github/scripts/check_issue_readiness.py @@ -0,0 +1,272 @@ +"""Determine whether an issue meets the `ready-for-dev` readiness criteria. + +The criteria are type-specific and tailored to extension contributions +(skills, plugins, integrations, and automations): + +- Bug reports (labeled `bug`): the Actual Behavior section must describe a + reproducible run and include a supported validation command (`uv`, + `pytest`, `python`, `pip`, `npm`, or `node`), plus a non-empty Acceptance + Criteria section with at least one checklist item. + +- Enhancements (labeled `enhancement`): the body must contain non-empty + Desired Behavior and Acceptance Criteria sections, the latter with at + least one checklist item. + +GitHub issue forms render each field as an `###