Release 0.2.1

.devcontainer/scripts/post-create.sh

@@ -20,8 +20,10 @@ fi
 
 # 2. Install Node.js
 if ! command -v node &> /dev/null; then
-    echo "Installing Node.js 20.x..."
-    curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
+    NODE_MAJOR=$(tr -d 'v\n' < .nvmrc 2>/dev/null | cut -d'.' -f1)
+    NODE_MAJOR=${NODE_MAJOR:-20}
+    echo "Installing Node.js ${NODE_MAJOR}.x..."
+    curl -fsSL "https://deb.nodesource.com/setup_${NODE_MAJOR}.x" | bash -
     apt-get install -y nodejs
 fi
 NODE_VERSION=$(node --version)

.github/CODEOWNERS

@@ -0,0 +1,8 @@
+# CODEOWNERS — default reviewers for pull requests
+# Docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+#
+# Each line defines a file pattern and the GitHub users/teams required to review
+# changes to matching files. Later rules take precedence over earlier ones.
+
+# Default: all files require review from the maintainer
+*                               @c-vigo

.github/ISSUE_TEMPLATE/bug_report.yml → .github/ISSUE_TEMPLATE/bug.yml

@@ -72,3 +72,17 @@ body:
       description: |
         If you have ideas on how to fix this, please describe them here
       placeholder: Optional - describe potential solutions...
+  - type: dropdown
+    id: changelog-category
+    attributes:
+      label: Changelog Category
+      description: |
+        Under which CHANGELOG.md section should this fix appear?
+      options:
+        - Fixed
+        - Security
+        - Changed
+        - No changelog needed
+      default: 0
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/chore.yml

@@ -0,0 +1,93 @@
+---
+name: Chore
+description: General task, CI/build change, or maintenance work item
+title: '[CHORE] '
+labels: ['chore']
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template for general tasks, CI/build changes, dependency
+        updates, or any maintenance work that doesn't fit bug/feature/refactor/docs.
+  - type: dropdown
+    id: chore-type
+    attributes:
+      label: Chore Type
+      description: What kind of chore is this?
+      options:
+        - General task
+        - CI / Build change
+        - Dependency update
+        - Configuration change
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the work
+      placeholder: Describe what needs to be done...
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: Acceptance Criteria
+      description: |
+        Define what needs to be completed for this to be considered done
+      placeholder: |
+        - [ ] Criterion 1
+        - [ ] Criterion 2
+        - [ ] Criterion 3
+    validations:
+      required: true
+  - type: textarea
+    id: implementation-notes
+    attributes:
+      label: Implementation Notes
+      description: |
+        Any technical notes, target files/workflows, or approach suggestions
+      placeholder: |
+        Technical details, target files, approach, dependencies, etc.
+  - type: textarea
+    id: related-issues
+    attributes:
+      label: Related Issues
+      description: Link to any related issues or pull requests
+      placeholder: 'Related to #123, Blocks #456, etc.'
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: Select the priority level
+      options:
+        - Low
+        - Medium
+        - High
+        - Critical
+    validations:
+      required: true
+  - type: dropdown
+    id: changelog-category
+    attributes:
+      label: Changelog Category
+      description: |
+        Under which CHANGELOG.md section should this appear?
+      options:
+        - Added
+        - Changed
+        - Fixed
+        - Removed
+        - Security
+        - No changelog needed
+      default: 5
+    validations:
+      required: true
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Any other relevant information
+      placeholder: Additional notes, error logs, workflow run links, etc.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Documentation
+    url: https://github.com/vig-os/sync-issues-action/tree/dev/docs
+    about: Browse project documentation before opening an issue

.github/ISSUE_TEMPLATE/discussion.yml

@@ -0,0 +1,70 @@
+---
+name: Discussion
+description: Discuss a new idea, approach, or open question
+title: '[DISCUSSION] '
+labels: ['discussion']
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template for open-ended discussions: new ideas, design
+        questions, trade-off analysis, or anything that benefits from
+        team input before becoming actionable work.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: |
+        A clear description of the topic, idea, or question you want
+        to discuss
+      placeholder: Describe the topic...
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: Context / Motivation
+      description: |
+        Why is this discussion relevant now? What triggered it?
+      placeholder: Background, observations, pain points, etc.
+    validations:
+      required: true
+  - type: textarea
+    id: options
+    attributes:
+      label: Options / Alternatives
+      description: |
+        If you've already considered approaches, list them here
+      placeholder: |
+        1. Option A — ...
+        2. Option B — ...
+  - type: textarea
+    id: open-questions
+    attributes:
+      label: Open Questions
+      description: |
+        Specific questions you'd like the team to weigh in on
+      placeholder: |
+        - Question 1?
+        - Question 2?
+  - type: textarea
+    id: related-issues
+    attributes:
+      label: Related Issues
+      description: Link to any related issues or pull requests
+      placeholder: 'Related to #123, see also #456'
+  - type: dropdown
+    id: changelog-category
+    attributes:
+      label: Changelog Category
+      description: |
+        Discussions rarely need a changelog entry. Change if this
+        leads directly to a visible change.
+      options:
+        - No changelog needed
+        - Added
+        - Changed
+      default: 0
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,85 @@
+---
+name: Documentation
+description: Request a documentation update or addition
+title: '[DOCS] '
+labels: ['docs']
+assignees: []
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template for documentation changes. Important: editable
+        documentation lives in `docs/templates/`. Generated files like
+        `CONTRIBUTE.md` and `README.md` must not be edited directly —
+        run `just docs` to regenerate them after editing the template.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: |
+        Describe the documentation change or addition needed
+      placeholder: Describe what needs to be documented...
+    validations:
+      required: true
+  - type: dropdown
+    id: doc-type
+    attributes:
+      label: Documentation Type
+      description: What kind of documentation change is this?
+      options:
+        - Update existing documentation
+        - Add new documentation
+        - Fix incorrect or outdated content
+        - Improve clarity or structure
+    validations:
+      required: true
+  - type: textarea
+    id: target-files
+    attributes:
+      label: Target Files
+      description: |
+        Which files need to be modified? Remember: edit templates in
+        `docs/templates/`, not generated files.
+      placeholder: |
+        - docs/templates/CONTRIBUTE.md.j2 (source template)
+        - docs/RELEASE_CYCLE.md
+    validations:
+      required: true
+  - type: textarea
+    id: related-code-changes
+    attributes:
+      label: Related Code Changes
+      description: |
+        If this docs update accompanies a code change, reference the
+        issue or PR
+      placeholder: 'Related to #123, follows up on PR #456'
+  - type: textarea
+    id: acceptance-criteria
+    attributes:
+      label: Acceptance Criteria
+      description: Define what "done" looks like for this documentation change
+      placeholder: |
+        - [ ] Template updated in docs/templates/
+        - [ ] Generated files regenerated with `just docs`
+        - [ ] Content is accurate and complete
+    validations:
+      required: true
+  - type: dropdown
+    id: changelog-category
+    attributes:
+      label: Changelog Category
+      description: |
+        Under which CHANGELOG.md section should this appear?
+      options:
+        - Changed
+        - Added
+        - No changelog needed
+      default: 2
+    validations:
+      required: true
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Any other relevant information
+      placeholder: Screenshots, examples, links to related documentation...

.github/ISSUE_TEMPLATE/feature_request.yml → .github/ISSUE_TEMPLATE/feature.yml

@@ -2,7 +2,7 @@
 name: Feature Request
 description: Suggest a new feature or enhancement
 title: '[FEATURE] '
-labels: ['enhancement']
+labels: ['feature']
 assignees: []
 body:
   - type: markdown
@@ -58,3 +58,16 @@ body:
       placeholder: |
         - Who would benefit from this feature?
         - Is this a breaking change or backward compatible?
+  - type: dropdown
+    id: changelog-category
+    attributes:
+      label: Changelog Category
+      description: |
+        Under which CHANGELOG.md section should this feature appear?
+      options:
+        - Added
+        - Changed
+        - No changelog needed
+      default: 0
+    validations:
+      required: true