fix labels

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,6 @@
-name: 🐞 Bug Report
-description: File a Bug report in Java Integration
-title: "🐞: "
-labels: [ "type:bug", "triage" ]
+name: Bug report
+description: Report broken or incorrect behavior in an Allure Java integration.
+type: bug
 assignees: []
 body:
   - type: markdown

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,32 @@
+name: Feature request
+description: Suggest a user-facing feature or improvement.
+type: feature
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for suggesting an improvement for Allure Java. Please describe the outcome you need, not only a possible implementation.
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem should this solve?
+      description: Describe the workflow, limitation, or user need behind the request.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: What would you like to happen?
+      description: Describe the behavior or capability you want Allure Java to provide.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Share any current workaround or alternative design you have considered.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Add examples, links, screenshots, or related issues.

.github/ISSUE_TEMPLATE/task.yml

@@ -0,0 +1,16 @@
+name: Task
+description: Track internal maintenance or repository work.
+type: task
+body:
+  - type: textarea
+    id: goal
+    attributes:
+      label: Goal
+      description: Describe the maintenance, cleanup, or repository task.
+    validations:
+      required: true
+  - type: textarea
+    id: details
+    attributes:
+      label: Details
+      description: Add relevant context, constraints, links, or acceptance criteria.

.github/dependabot.yml

@@ -5,11 +5,11 @@ updates:
     schedule:
       interval: "daily"
     labels:
-      - "type:dependencies"
+      - "pr:dependencies"
 
   - package-ecosystem: "gradle"
     directory: "/"
     schedule:
       interval: "daily"
     labels:
-      - "type:dependencies"
+      - "pr:dependencies"

.github/PULL_REQUEST_TEMPLATE.md → .github/pull_request_template.md

@@ -1,7 +1,7 @@
 <!---
-Thank you so much for sending us a pull request! 
+Thank you so much for sending us a pull request!
 
-Make sure you have a clear name for your pull request. 
+Make sure you have a clear name for your pull request.
 The name should start with a capital letter and no dot is required in the end of the sentence.
 To link the request with issues use the following notation: (fixes #123, fixes #321\)
 
@@ -12,12 +12,14 @@ An example of good pull request names:
 -->
 
 ### Context
+
 <!---
 Describe the problem or feature in addition to a link to the issues
 -->
 
 #### Checklist
+
 - [ ] [Sign Allure CLA][cla]
 - [ ] Provide unit tests
 
-[cla]: https://cla-assistant.io/accept/allure-framework/allure2
+[cla]: https://cla-assistant.io/accept/allure-framework/allure-java

.github/release.yml

@@ -1,25 +1,29 @@
 # release.yml
 
 changelog:
+  exclude:
+    labels:
+      - 'pr:invalid'
+      - 'pr:tests'
   categories:
     - title: '🚀 New Features'
       labels:
-        - 'type:new feature'
+        - 'pr:new feature'
     - title: '🔬 Improvements'
       labels:
-        - 'type:improvement'
+        - 'pr:improvement'
     - title: '🐞 Bug Fixes'
       labels:
-        - 'type:bug'
+        - 'pr:bug'
     - title: '⬆️ Dependency Updates'
       labels:
-        - 'type:dependencies'
+        - 'pr:dependencies'
     - title: '📖 Documentation improvements'
       labels:
-        - 'type:documentation'
+        - 'pr:documentation'
     - title: '⛔️ Security'
       labels:
-        - 'type:security'
+        - 'pr:security'
     - title: '👻 Internal changes'
       labels:
-        - 'type:internal'
+        - 'pr:internal'

.github/workflows/pr-labels.yml

@@ -0,0 +1,61 @@
+name: Pull Request Labels
+
+on:
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - synchronize
+      - ready_for_review
+      - labeled
+      - unlabeled
+      - edited
+
+permissions:
+  contents: read
+  pull-requests: read
+  issues: read
+
+jobs:
+  require-pr-label:
+    name: Require exactly one pr label
+    runs-on: ubuntu-latest
+    steps:
+      - name: Validate release notes label
+        env:
+          GH_TOKEN: ${{ github.token }}
+          PR_NUMBER: ${{ github.event.pull_request.number }}
+        shell: bash
+        run: |
+          labels="$(gh api "repos/${GITHUB_REPOSITORY}/issues/${PR_NUMBER}/labels" --jq '.[].name')"
+          pr_labels="$(printf '%s\n' "${labels}" | grep '^pr:' || true)"
+
+          if [ -z "${pr_labels}" ]; then
+            count=0
+          else
+            count="$(printf '%s\n' "${pr_labels}" | wc -l | tr -d ' ')"
+          fi
+
+          if [ "${count}" -eq 1 ]; then
+            echo "Found PR release-note label: ${pr_labels}"
+            exit 0
+          fi
+
+          {
+            echo "Pull requests must have exactly one label with the pr: prefix."
+            echo "Found ${count} pr: labels."
+            if [ "${count}" -gt 0 ]; then
+              printf 'Matching labels:\n'
+              printf '%s\n' "${pr_labels}" | sed 's/^/- /'
+            fi
+            echo
+            echo "Available labels on this PR:"
+            if [ -n "${labels}" ]; then
+              printf '%s\n' "${labels}" | sed 's/^/- /'
+            else
+              echo "- <none>"
+            fi
+          } >> "${GITHUB_STEP_SUMMARY}"
+
+          echo "::error title=Invalid pr: label count::Pull requests must have exactly one label with the pr: prefix. Found ${count}."
+          exit 1