mirrors/z3
3
0
Fork 0
mirror of https://github.com/Z3Prover/z3 synced 2025-12-06 03:52:24 +00:00
Code Activity

update workflows

Browse source
This commit is contained in:
Don Syme 2025-09-17 11:33:24 +01:00
parent db8206d265
commit 7268136bb6
9 changed files with 130 additions and 55 deletions
Download patch file Download diff file Expand all files Collapse all files

30
.github/workflows/pr-fix.lock.yml generated vendored
View file

@ -2,7 +2,7 @@
# To update this file, edit the corresponding .md file and run:
# gh aw compile
#
# Effective stop-time: 2025-09-19 10:02:59
# Effective stop-time: 2025-09-19 10:32:53
name: "PR Fix"
on:
@ -859,7 +859,7 @@ jobs:
},
},
{
name: "add-issue-label",
name: "add-issue-labels",
description: "Add labels to a GitHub issue or pull request",
inputSchema: {
type: "object",
@ -1071,7 +1071,7 @@ jobs:
WORKFLOW_NAME="PR Fix"
# Check stop-time limit
STOP_TIME="2025-09-19 10:02:59"
STOP_TIME="2025-09-19 10:32:53"
echo "Checking stop-time limit: $STOP_TIME"
# Convert stop time to epoch seconds
@ -1171,6 +1171,22 @@ jobs:
## Adding a Comment to an Issue or Pull Request, Creating an Issue, Pushing Changes to Branch, Reporting Missing Tools or Functionality
**IMPORTANT**: To do the actions mentioned in the header of this section, use the **safe-outputs** tools, do NOT attempt to use `gh`, do NOT attempt to use the GitHub API. You don't have write access to the GitHub repo.
**Adding a Comment to an Issue or Pull Request**
To add a comment to an issue or pull request, use the add-issue-comments tool from the safe-outputs MCP
**Creating an Issue**
To create an issue, use the create-issue tool from the safe-outputs MCP
**Pushing Changes to Pull Request Branch**
To push changes to the branch of a pull request:
1. Make any file changes directly in the working directory
2. Add and commit your changes to the local copy of the pull request branch. Be careful to add exactly the files you intend, and check there are no extra files left un-added. Check you haven't deleted or changed any files you didn't intend to.
3. Push the branch to the repo by using the push-to-pr-branch tool from the safe-outputs MCP
EOF
- name: Print prompt to step summary
run: |
@ -1498,7 +1514,7 @@ jobs:
return 1; // Only one pull request allowed
case "create-pull-request-review-comment":
return 10; // Default to 10 review comments allowed
case "add-issue-label":
case "add-issue-labels":
return 5; // Only one labels operation allowed
case "update-issue":
return 1; // Only one issue update allowed
@ -1751,10 +1767,10 @@ jobs:
);
}
break;
case "add-issue-label":
case "add-issue-labels":
if (!item.labels || !Array.isArray(item.labels)) {
errors.push(
`Line ${i + 1}: add-issue-label requires a 'labels' array field`
`Line ${i + 1}: add-issue-labels requires a 'labels' array field`
);
continue;
}
@ -1764,7 +1780,7 @@ jobs:
)
) {
errors.push(
`Line ${i + 1}: add-issue-label labels array must contain only strings`
`Line ${i + 1}: add-issue-labels labels array must contain only strings`
);
continue;
}