microsoft / microsoft/devsquad-copilot
[implement] Do not commit structure.md; drop tasks.md once work items exist on the board
Open
Nobody has claimed this yet.
bug
- Dominant language
- No language data
- Stars
- 44
- Forks
- 10
- Avg merge
- 6h 49m
- Merged PRs (30d)
- 1
Description
Recurring problem across projects.
Observed behavior
- A temporary
structure.mdfile was created and committed. tasks.mdremains committed even after the work items have been created on the board (GitHub Issues or Azure DevOps).
Desired behavior
structure.mdis treated as temporary and never committed.- When work items are created on the board,
tasks.mdis either not committed or is removed automatically once the items land as issues/work items.
Acceptance criteria
- Implementation flow does not commit
structure.md. - After board sync,
tasks.mdis cleaned up automatically or its non-creation is enforced.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the implementation flow that creates or commits structure.md and tasks.md, then follow the board-sync entry point for GitHub Issues or Azure DevOps. Confirm where temporary files are handled and how sync completion is detected. Done means structure.md is not committed and tasks.md is removed or never committed after work items are created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100