Copilot commented on code in PR #13042:
URL: https://github.com/apache/cloudstack/pull/13042#discussion_r3098494378
##########
.github/workflows/issue-triage-agent.lock.yml:
##########
@@ -53,11 +53,11 @@ jobs:
comment_repo: ""
steps:
- name: Setup Scripts
- uses:
github/gh-aw/actions/setup@58d1d157fbac0f1204798500faefc4f7461ebe28 # v0.45.0
+ uses:
github/gh-aw/actions/setup@ce1794953e0ec42adc41b6fca05e02ab49ee21c3 # v0.68.3
with:
destination: /opt/gh-aw/actions
- name: Check workflow file timestamps
- uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd #
v8
+ uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 #
v9.0.0
Review Comment:
The workflow is now pinned to `github/gh-aw` setup v0.68.3, but the file
header still states it was generated by gh-aw v0.45.0. This suggests the lock
file wasn’t regenerated with the new gh-aw version, which can lead to
mismatches between the workflow content and the scripts shipped by the pinned
gh-aw commit. Regenerate this lock file using the updated gh-aw version (and
align the version in the PR description if v0.68.3 is intended).
##########
.github/workflows/daily-repo-status.lock.yml:
##########
@@ -784,12 +784,12 @@ jobs:
total_count: ${{ steps.missing_tool.outputs.total_count }}
steps:
- name: Setup
- uses:
github/gh-aw/actions/setup@58d1d157fbac0f1204798500faefc4f7461ebe28 # v0.45.
+ uses:
github/gh-aw/actions/setup@ce1794953e0ec42adc41b6fca05e02ab49ee21c3 # v0.45.
with:
destination: /opt/gh-aw/
- name: Download agent output
continue-on-error:
- uses:
actions/download-artifact@018cc2cf5baa6db3ef3c5f8a56943fffe632ef53 # v6.0.
+ uses:
actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v6.0.
with:
Review Comment:
`continue-on-error` is present with no boolean value, and the
download-artifact pin’s inline version comment is inconsistent with the SHA (it
still reads `# v6.0.` even though the SHA corresponds to v8.0.1). Both indicate
the lock file wasn’t cleanly regenerated and may be invalid YAML. Re-render
this section so booleans are explicit and the pinned SHA/version comments are
consistent.
##########
.github/workflows/daily-repo-status.lock.yml:
##########
@@ -54,11 +54,11 @@ jobs:
comment_repo: ""
steps:
- name: Setup
- uses:
github/gh-aw/actions/setup@58d1d157fbac0f1204798500faefc4f7461ebe28 # v0.45.
+ uses:
github/gh-aw/actions/setup@ce1794953e0ec42adc41b6fca05e02ab49ee21c3 # v0.45.
with:
destination: /opt/gh-aw/
- name: Check workflow file
- uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd #
+ uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 #
Review Comment:
This lock workflow appears to have been corrupted/truncated: the gh-aw setup
line comment is cut off (`# v0.45.`) and other fields nearby in the file are
incomplete (e.g., `runs-on: ubuntu-`, empty `permissions:` entries, etc.),
which will make the workflow invalid or non-runnable. Please re-generate
`daily-repo-status.lock.yml` with the updated gh-aw tooling so all YAML values
are complete and consistent (including the generator/version metadata in the
header).
##########
.github/workflows/daily-repo-status.lock.yml:
##########
@@ -704,13 +704,13 @@ jobs:
await main();
- name: Upload sanitized agent
if: always() && env.
- uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f
# v6.0.
+ uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a
# v6.0.
with:
name: agent-
path: ${{ env.GH_AW_AGENT_OUTPUT }}
Review Comment:
Several step configurations here have truncated/empty required values (e.g.,
`if: always() && env.` and artifact `name: agent-`, plus missing
`if-no-files-found`). These null/partial values are not valid for GitHub
Actions and will cause the workflow to fail to parse or run. Re-generate the
lock file so these inputs/conditions are fully rendered (e.g., complete env var
checks, full artifact names, explicit `if-no-files-found` behavior).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
