Skip to content

docs: update tool version issue template#1096

Merged
Ron (rjaegers) merged 3 commits into
mainfrom
docs/update-tool-version-issue-template
Jan 22, 2026
Merged

docs: update tool version issue template#1096
Ron (rjaegers) merged 3 commits into
mainfrom
docs/update-tool-version-issue-template

Conversation

@rjaegers
Copy link
Copy Markdown
Member

🚀 Hey, I have created a Pull Request

Description of changes

This pull request improves the workflow for creating tool version evaluation issues by introducing a dedicated markdown template and updating the automation to use it. The changes make the process clearer, more maintainable, and easier for contributors to follow.

Workflow improvements:

  • Added a new markdown template file .github/TOOL_VERSION_ISSUE_TEMPLATE.md that provides a detailed checklist, usage instructions, and notes for evaluating and updating tool versions. This replaces the previous inline issue body and makes future updates easier.
  • Updated the workflow in .github/workflows/issue-creation-tool-versions.yml to use the new template file for issue creation, streamlining the process and ensuring consistency in issue formatting.
  • Improved repository checkout in the workflow by using sparse checkout to only retrieve the new template file, reducing unnecessary downloads.

Automation reliability:

  • Enhanced the logic for closing previous issues by handling cases where no previous issue exists and ensuring the close reason is set to "completed". Also, made unpinning robust against errors.

Documentation and permissions:

  • Added a comment to clarify required repository permissions for the workflow to run correctly.

✔️ Checklist

  • I have followed the contribution guidelines for this repository
  • I have added tests for new behavior, and have not broken any existing tests
  • I have added or updated relevant documentation
  • I have verified that all added components are accounted for in the SBOM

@rjaegers Ron (rjaegers) requested a review from a team as a code owner January 22, 2026 12:26
Copilot AI review requested due to automatic review settings January 22, 2026 12:26
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request refactors the tool version evaluation issue creation workflow by extracting the issue template from inline YAML to a dedicated markdown file, improving maintainability and clarity.

Changes:

  • Introduced a new markdown template file (.github/TOOL_VERSION_ISSUE_TEMPLATE.md) containing the complete issue checklist and instructions
  • Updated the workflow (.github/workflows/issue-creation-tool-versions.yml) to reference the external template file instead of an inline body
  • Enhanced workflow robustness with improved sparse checkout, better error handling for issue closing/unpinning, and clearer permissions documentation

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/issue-creation-tool-versions.yml Refactored to use external template file, added sparse checkout, improved issue closing logic, and documented permissions
.github/TOOL_VERSION_ISSUE_TEMPLATE.md New template file with restructured checklist format using tables, emoji headers, and improved documentation

Comment thread .github/TOOL_VERSION_ISSUE_TEMPLATE.md Outdated
Comment thread .github/workflows/issue-creation-tool-versions.yml
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 22, 2026

⚠️MegaLinter analysis: Success with warnings

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 20 0 0 0.53s
✅ DOCKERFILE hadolint 3 0 0 0.65s
✅ GHERKIN gherkin-lint 6 0 0 2.46s
✅ JSON npm-package-json-lint yes no no 0.35s
✅ JSON prettier 21 4 0 0 0.53s
✅ JSON v8r 21 0 0 6.9s
✅ MARKDOWN markdownlint 12 0 0 0 0.99s
✅ MARKDOWN markdown-table-formatter 12 0 0 0 0.26s
✅ REPOSITORY checkov yes no no 17.65s
✅ REPOSITORY gitleaks yes no no 0.51s
✅ REPOSITORY git_diff yes no no 0.01s
✅ REPOSITORY grype yes no no 28.07s
✅ REPOSITORY secretlint yes no no 0.92s
✅ REPOSITORY syft yes no no 1.85s
✅ REPOSITORY trivy yes no no 7.63s
✅ REPOSITORY trivy-sbom yes no no 0.23s
✅ REPOSITORY trufflehog yes no no 2.3s
⚠️ SPELL lychee 80 2 0 57.41s
✅ YAML prettier 28 0 0 0 0.95s
✅ YAML v8r 28 0 0 7.89s
✅ YAML yamllint 28 0 0 0.82s

Detailed Issues

⚠️ SPELL / lychee - 2 errors
[IGNORED] docker://pandoc/extra:3.7.0@sha256:a703d335fa237f8fc3303329d87e2555dca5187930da38bfa9010fa4e690933a | Unsupported: Error creating request client: builder error for url (docker://pandoc/extra:3.7.0@sha256:a703d335fa237f8fc3303329d87e2555dca5187930da38bfa9010fa4e690933a)
[ERROR] https://docs.sigstore.dev/cosign/verifying/verify/ | Network error: error sending request for url (https://docs.sigstore.dev/cosign/verifying/verify/) Maybe a certificate error?
[IGNORED] https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/philips-software/amp-devcontainer | Unsupported: Error creating request client: builder error for url (vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/philips-software/amp-devcontainer)
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads | Network error: Forbidden
📝 Summary
---------------------
🔍 Total..........126
✅ Successful.....122
⏳ Timeouts.........0
🔀 Redirected.......0
👻 Excluded.........0
❓ Unknown..........0
🚫 Errors...........2

Errors in README.md
[ERROR] https://docs.sigstore.dev/cosign/verifying/verify/ | Network error: error sending request for url (https://docs.sigstore.dev/cosign/verifying/verify/) Maybe a certificate error?

Errors in .github/TOOL_VERSION_ISSUE_TEMPLATE.md
[403] https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads | Network error: Forbidden

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.3.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,DOCKERFILE_HADOLINT,GHERKIN_GHERKIN_LINT,JSON_V8R,JSON_PRETTIER,JSON_NPM_PACKAGE_JSON_LINT,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_GRYPE,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 22, 2026

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-base:edgeghcr.io/philips-software/amp-devcontainer-base:pr-1096

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 167.73 MB 167.73 MB +426 B (+0%) 🔼
linux/arm64 160.76 MB 160.76 MB 290 B (0%) 🔽

Copilot AI review requested due to automatic review settings January 22, 2026 12:35
@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

Comment thread .github/workflows/issue-creation-tool-versions.yml
Comment thread .github/TOOL_VERSION_ISSUE_TEMPLATE.md
@github-actions
Copy link
Copy Markdown
Contributor

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-rust:edgeghcr.io/philips-software/amp-devcontainer-rust:pr-1096

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 548.14 MB 548.14 MB +431 B (+0%) 🔼
linux/arm64 502.87 MB 502.87 MB 375 B (0%) 🔽

@github-actions
Copy link
Copy Markdown
Contributor

📦 Container Size Analysis

Note

Comparing ghcr.io/philips-software/amp-devcontainer-cpp:edgeghcr.io/philips-software/amp-devcontainer-cpp:pr-1096

📈 Size Comparison Table

OS/Platform Previous Current Change Trend
linux/amd64 683.73 MB 683.73 MB +436 B (+0%) 🔼
linux/arm64 665.68 MB 665.68 MB 377 B (0%) 🔽

@github-actions
Copy link
Copy Markdown
Contributor

Test Results

 7 files  ±0   7 suites  ±0   3m 45s ⏱️ +9s
33 tests ±0  33 ✅ ±0  0 💤 ±0  0 ❌ ±0 
69 runs  ±0  69 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit d857162. ± Comparison against base commit f42f104.

@rjaegers Ron (rjaegers) added this pull request to the merge queue Jan 22, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Jan 22, 2026
@rjaegers Ron (rjaegers) added this pull request to the merge queue Jan 22, 2026
github-merge-queue Bot pushed a commit that referenced this pull request Jan 22, 2026
* docs: update tool version issue template

* docs: minor updates to template

* docs: ignore MD041; first line should be a top-level heading
@rjaegers Ron (rjaegers) removed this pull request from the merge queue due to a manual request Jan 22, 2026
@rjaegers Ron (rjaegers) added this pull request to the merge queue Jan 22, 2026
Merged via the queue into main with commit e5651d1 Jan 22, 2026
42 checks passed
@rjaegers Ron (rjaegers) deleted the docs/update-tool-version-issue-template branch January 22, 2026 19:22
@github-actions
Copy link
Copy Markdown
Contributor

Pull Request Report (#1096)

Static measures

Description Value
Number of added lines 58
Number of deleted lines 41
Number of changed files 2
Number of commits 3
Number of reviews 4
Number of comments (w/o review comments) 6
Number of reviews that contains a comment to resolve 3
Number of reviews that requested a change from the author 0
Number of reviews that approved the Pull Request 1
Get the total number of participants of a Pull Request 6

Time related measures

Description Value
PR lead time (from creation to close of PR) 6.9 Hours
Time that was spend on the branch before the PR was created 1.2 Min
Time that was spend on the branch before the PR was merged 7 Hours
Time to merge after last review 5.4 Hours

Status check related measures

Description Value
Total runtime for last status check run (Workflow for PR) 43.8 Min
Total time spend in last status check run on PR 6.8 Hours

@github-actions
Copy link
Copy Markdown
Contributor

🎉 Hooray! The changes in this pull request went live with the release of v6.7.1 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants