mirrors/z3
3
0
Fork 0
mirror of https://github.com/Z3Prover/z3 synced 2025-11-02 12:37:52 +00:00
Code Activity

improve improvers

Browse source
This commit is contained in:
Don Syme 2025-09-17 11:03:23 +01:00
parent 5b70f75d89
commit db8206d265
9 changed files with 34 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

15
.github/workflows/daily-backlog-burner.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 01:41:09
# Effective stop-time: 2025-09-19 10:02:59
name: "Daily Backlog Burner"
"on":
@ -527,7 +527,7 @@ jobs:
WORKFLOW_NAME="Daily Backlog Burner"
# Check stop-time limit
STOP_TIME="2025-09-19 01:41:09"
STOP_TIME="2025-09-19 10:02:59"
echo "Checking stop-time limit: $STOP_TIME"
# Convert stop time to epoch seconds
@ -564,7 +564,7 @@ jobs:
1. Backlog research (if not done before).
1a. Check carefully if an open issue with title "${{ github.workflow }} - Research, Roadmap and Plan" exists using `search_issues`. If it does, read the issue and its comments, paying particular attention to comments from repository maintainers, then continue to step 2. If the issue doesn't exist, follow the steps below to create it:
1a. Check carefully if an open issue with label "daily-backlog-burner-plan" exists using `search_issues`. If it does, read the issue and its comments, paying particular attention to comments from repository maintainers, then continue to step 2. If the issue doesn't exist, follow the steps below to create it:
1b. Do some deep research into the backlog in this repo.
- Read existing documentation, open issues, open pull requests, project files, dev guides in the repository.
@ -577,7 +577,7 @@ jobs:
- Identify any patterns or common themes among the issues, such as recurring bugs, feature requests, or areas of improvement.
- Look for any issues that may be duplicates or closely related to each other, and consider whether they can be consolidated or linked together.
1c. Use this research to create an issue with title "${{ github.workflow }} - Research, Roadmap and Plan". This issue should be a comprehensive plan for dealing with the backlog in this repo, and summarize your findings from the backlog research, including any patterns or themes you identified, and your recommendations for addressing the backlog. Then exit this entire workflow.
1c. Use this research to create an issue with title "${{ github.workflow }} - Research, Roadmap and Plan" and label "daily-backlog-burner-plan". This issue should be a comprehensive plan for dealing with the backlog in this repo, and summarize your findings from the backlog research, including any patterns or themes you identified, and your recommendations for addressing the backlog. Then exit this entire workflow.
2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue.
@ -611,11 +611,10 @@ jobs:
4c. After creation, check the pull request to ensure it is correct, includes all expected files, and doesn't include any unwanted files or changes. Make any necessary corrections by pushing further commits to the branch.
4d. Add a very brief comment to the issue from step 1a if it exists, saying you have worked on the particular goal and linking to the pull request you created.
5. At the end of your work, add a very, very brief comment (at most two-sentences) to the issue from step 1a, saying you have worked on the particular goal, linking to any pull request you created, and indicating whether you made any progress or not.
5. If you didn't succeed, create an issue with title starting with "${{ github.workflow }}", summarizing similar information to above.
6. If you encounter any unexpected failures or have questions, add comments to the pull request or issue to seek clarification or assistance.
6. If you encounter any unexpected failures or have questions, add
comments to the pull request or issue to seek clarification or assistance.
> NOTE: Never make direct pushes to the default (main) branch. Always create a pull request. The default (main) branch is protected and you will not be able to push to it.