mirrors/z3
3
0
Fork 0
mirror of https://github.com/Z3Prover/z3 synced 2025-10-04 15:03:57 +00:00
Code Activity

backlog burner

Browse source
This commit is contained in:
Don Syme 2025-09-17 02:20:48 +01:00
parent ba4c9238c0
commit 81da4be228
2 changed files with 18 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

15
.github/workflows/daily-backlog.lock.yml → .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: # To update this file, edit the corresponding .md file and run:
# gh aw compile # gh aw compile
# #
# Effective stop-time: 2025-09-19 01:02:50 # Effective stop-time: 2025-09-19 01:20:03
name: "Daily Backlog Burner" name: "Daily Backlog Burner"
"on": "on":
@ -527,7 +527,7 @@ jobs:
WORKFLOW_NAME="Daily Backlog Burner" WORKFLOW_NAME="Daily Backlog Burner"
# Check stop-time limit # Check stop-time limit
STOP_TIME="2025-09-19 01:02:50" STOP_TIME="2025-09-19 01:20:03"
echo "Checking stop-time limit: $STOP_TIME" echo "Checking stop-time limit: $STOP_TIME"
# Convert stop time to epoch seconds # Convert stop time to epoch seconds
@ -567,12 +567,17 @@ jobs:
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 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:
1b. Do some deep research into the backlog in this repo. 1b. Do some deep research into the backlog in this repo.
- Read existing documentation, issues, pull requests, project files, dev guides in the repository. - Read existing documentation, open issues, open pull requests, project files, dev guides in the repository.
- Look at any existing open issues and pull requests that are part of the backlog - not feature requests, but bugs, chores, maintenance tasks and so on. - Carefully research the entire backlog of issues and pull requests. Read through every single issue, even if it takes you quite a while, and understand what each issue is about, its current status, any comments or discussions on it, and any relevant context.
- Understand the main features of the project, its goals, and its target audience. - Understand the main features of the project, its goals, and its target audience.
- If you find a relevant roadmap document, read it carefully and use it to inform your understanding of the project's status and priorities. - If you find a relevant roadmap document, read it carefully and use it to inform your understanding of the project's status and priorities.
- Group, categorize, and prioritize the issues in the backlog based on their importance, urgency, and relevance to the project's goals.
- Estimate whether issues are clear and actionable, or whether they need more information or clarification, or whether they are out of date and can be closed.
- Estimate the effort required to address each issue, considering factors such as complexity, dependencies, and potential impact.
- 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 write an issue with title "${{ github.workflow }} - Research, Roadmap and Plan", then exit this entire workflow. 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.
2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue. 2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue.

11
.github/workflows/daily-backlog.md → .github/workflows/daily-backlog-burner.md vendored
View file

@ -46,12 +46,17 @@ Your name is ${{ github.workflow }}. Your job is to act as an agentic coder for
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 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:
1b. Do some deep research into the backlog in this repo. 1b. Do some deep research into the backlog in this repo.
- Read existing documentation, issues, pull requests, project files, dev guides in the repository. - Read existing documentation, open issues, open pull requests, project files, dev guides in the repository.
- Look at any existing open issues and pull requests that are part of the backlog - not feature requests, but bugs, chores, maintenance tasks and so on. - Carefully research the entire backlog of issues and pull requests. Read through every single issue, even if it takes you quite a while, and understand what each issue is about, its current status, any comments or discussions on it, and any relevant context.
- Understand the main features of the project, its goals, and its target audience. - Understand the main features of the project, its goals, and its target audience.
- If you find a relevant roadmap document, read it carefully and use it to inform your understanding of the project's status and priorities. - If you find a relevant roadmap document, read it carefully and use it to inform your understanding of the project's status and priorities.
- Group, categorize, and prioritize the issues in the backlog based on their importance, urgency, and relevance to the project's goals.
- Estimate whether issues are clear and actionable, or whether they need more information or clarification, or whether they are out of date and can be closed.
- Estimate the effort required to address each issue, considering factors such as complexity, dependencies, and potential impact.
- 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 write an issue with title "${{ github.workflow }} - Research, Roadmap and Plan", then exit this entire workflow. 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.
2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue. 2. Goal selection: build an understanding of what to work on and select a part of the roadmap to pursue.