LabelOps — PR Maintenance #181
labelops-pr-maintenance.lock.yml
on: schedule
Annotations
5 errors and 10 warnings
|
safe_outputs
2 safe output(s) failed:
- push_to_pull_request_branch: Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'fix/nullness-dropping-alias': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.
- push_to_pull_request_branch: Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'fix/19664-extension-overloads': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.
|
|
safe_outputs
✗ Message 3 (push_to_pull_request_branch) failed: Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'fix/19664-extension-overloads': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.
|
|
safe_outputs
Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'fix/19664-extension-overloads': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.
|
|
safe_outputs
✗ Message 1 (push_to_pull_request_branch) failed: Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'fix/nullness-dropping-alias': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.
|
|
safe_outputs
Failed to push changes: pushSignedCommits: refusing unsigned push for branch 'fix/nullness-dropping-alias': merge commit detected. GitHub's createCommitOnBranch GraphQL mutation cannot represent merge commits, symlinks (mode 120000), submodule entries (mode 160000), or executable bits (mode 100755). Rewrite the commits to use only regular files (mode 100644) with no merge commits, or set signed-commits: false if the repository does not require signed commits.
|
|
safe_outputs
push_to_pull_request_branch: failed to linearize merge commits: Failed to linearize f0a4fd6f552e68233015eb0a0aa26a5aa56537c2..HEAD as a single commit: No staged changes found after soft reset to f0a4fd6f552e68233015eb0a0aa26a5aa56537c2. The commit range may contain only no-op or empty commits. Ensure your commits contain actual file changes before pushing.; push may fail
|
|
safe_outputs
linearizeRangeAsCommit: rewrite failed; restored original HEAD 674cd6482a1f1b21856eb8f4a2ab15c8d6f2ff6b
|
|
safe_outputs
push_to_pull_request_branch: detected 1 merge commit(s) in range f0a4fd6f552e68233015eb0a0aa26a5aa56537c2..HEAD. Merge commits cannot be pushed as signed commits. Squashing the range into a single regular commit to preserve content. To avoid this, use 'git rebase' instead of 'git merge' when updating the PR branch.
|
|
safe_outputs
Could not check branch protection rules for "fix/19664-extension-overloads" (insufficient permissions): Resource not accessible by integration - https://docs.github.com/rest/branches/branch-protection#get-branch-protection
|
|
safe_outputs
⚠️ Code push operation 'push_to_pull_request_branch' failed — continuing with remaining safe outputs (add_comment messages will include a failure note)
|
|
safe_outputs
pushSignedCommits: merge commit 865791834737097c77516b125a57596b84277efe detected, refusing unsigned push fallback
|
|
safe_outputs
push_to_pull_request_branch: failed to linearize merge commits: Failed to linearize 72651feb44f7aeb3b0d8c1b14f5e45c0f74e1671..HEAD as a single commit: No staged changes found after soft reset to 72651feb44f7aeb3b0d8c1b14f5e45c0f74e1671. The commit range may contain only no-op or empty commits. Ensure your commits contain actual file changes before pushing.; push may fail
|
|
safe_outputs
linearizeRangeAsCommit: rewrite failed; restored original HEAD 865791834737097c77516b125a57596b84277efe
|
|
safe_outputs
push_to_pull_request_branch: detected 1 merge commit(s) in range 72651feb44f7aeb3b0d8c1b14f5e45c0f74e1671..HEAD. Merge commits cannot be pushed as signed commits. Squashing the range into a single regular commit to preserve content. To avoid this, use 'git rebase' instead of 'git merge' when updating the PR branch.
|
|
safe_outputs
Could not check branch protection rules for "fix/nullness-dropping-alias" (insufficient permissions): Resource not accessible by integration - https://docs.github.com/rest/branches/branch-protection#get-branch-protection
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
activation
Expired
|
275 KB |
sha256:357733762901e4e4e6889a5c6faed3e40595aea2981abed675b30d96c2b20c94
|
|
|
agent
|
1 MB |
sha256:1fd8dae59aef2d9dac15d72d37219e302ed1b4b9fbb8157f4839be3a1d01ff8a
|
|
|
detection
|
3.52 KB |
sha256:f5ca6a0df4db55d9ab5f42846cc5d4caf48bfaa09b109c37f789342156774fe2
|
|
|
safe-outputs-items
|
452 Bytes |
sha256:16f50de3e16d6b1bc364e6e6cdb1b3382614fd5a0f1b652c72eb79ec36f24ed8
|
|