chore: unify workflow titles and share issue templates org-wide

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -0,0 +1,27 @@
+name: Bug report
+description: Something went wrong
+labels: ["bug"]
+body:
+  - type: textarea
+    id: freeform
+    attributes:
+      label: Describe your issue
+      placeholder: 'I was doing ... I ran ... I expected ... I got ...'
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: The version of the CLI, Action or MCP server you ran.
+      placeholder: commit-check 2.19.0, commit-check-action v2.18.0, ...
+    validations:
+      required: false
+  - type: textarea
+    id: configuration
+    attributes:
+      label: cchk.toml or commit-check.toml
+      description: (auto-rendered as toml, no need for backticks)
+      render: toml
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Questions and ideas
+    url: https://github.com/commit-check/commit-check/discussions
+    about: Ask a question or share an idea in Discussions.
+  - name: Documentation
+    url: https://commit-check.com
+    about: Every rule and option, with examples.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,38 @@
+name: Feature request
+description: Suggest an idea for this project
+labels: ["enhancement"]
+
+body:
+  - type: markdown
+    attributes:
+      value: >-
+        Hi there!
+
+        We'd appreciate it if you could search the existing issues before filing
+        a feature request.
+
+  - type: textarea
+    attributes:
+      label: What's the problem this feature will solve?
+      description: >-
+        What are you trying to do, that you are unable to achieve with Commit Check as it currently stands?
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: >-
+        A clear and concise description of what you want to happen. Please use examples
+        of real-world use cases that this would help with, and how it solves the
+        problem described above.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: >-
+        Add any other context, links, etc. relevant to the feature request.
+    validations:
+      required: false

.github/dependabot.yml

@@ -1,13 +1,18 @@
+# Dependabot version updates.
 # https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+#
+# Same shape in every commit-check repository: monthly, one grouped pull
+# request per ecosystem, `chore(deps)` commit subjects.
+
 version: 2
 updates:
-  - package-ecosystem: "github-actions"
-    directory: "/"
+  - package-ecosystem: github-actions
+    directory: /
     schedule:
-      interval: "weekly"
-      day: "monday"
+      interval: monthly
     commit-message:
-      prefix: "ci"
+      prefix: chore
+      include: scope
     labels:
       - "dependencies"
     groups:

.github/workflows/commit-check.yml

@@ -16,7 +16,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           fetch-depth: 0  # Required for merge-base checks
-      - uses: commit-check/commit-check-action@a61779784a953fd9047c001c102cfeac5cf26964 # v2.17.1
+      - uses: commit-check/commit-check-action@bcbadb3fec596872bcae51074d8fdbea15c02ba5 # v2.18.0
         with:
           message: true
           branch: true

.github/workflows/pr-labeler.yml

@@ -4,7 +4,7 @@ on:
   workflow_call:
 
 concurrency:
-  group: pr-labeler-${{ github.ref }}
+  group: pr-labeler-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: true
 
 jobs:

.github/workflows/pre-commit.yml

@@ -1,4 +1,4 @@
-name: Run pre-commit
+name: pre-commit
 
 on:
   workflow_call:

.github/workflows/stale.yml

@@ -1,4 +1,4 @@
-name: Mark stale issues and pull requests
+name: Stale
 
 on:
   schedule:

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2023 shenxianpeng
+Copyright (c) 2023 Xianpeng Shen
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

profile/README.md

@@ -62,7 +62,7 @@ Conventional Branch, and sane subject lengths.
 # .pre-commit-config.yaml — feedback while the message is still being written
 repos:
   - repo: https://github.com/commit-check/commit-check
-    rev: v2.13.4
+    rev: v2.19.1
     hooks:
       - id: check-message
       - id: check-branch
@@ -113,7 +113,7 @@ reviewed, diffed, and rolled back like anything else you version.
   [many more](https://github.com/commit-check/commit-check-action/network/dependents)
 - 📖 MIT licensed, actively maintained, and itself following
   [Conventional Commits](https://www.conventionalcommits.org/) and
-  [Conventional Branch](https://conventional-branch.github.io/)
+  [Conventional Branch](https://conventionalbranch.org/)
 
 ## Get involved