microsoft / microsoft/devsquad-copilot
[engineering-practices] Verify branch protection when CI pipelines are created
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- No language data
- Stars
- 44
- Forks
- 10
- Avg merge
- 6h 49m
- Merged PRs (30d)
- 1
Description
When agents create CI (and CD) pipelines, there is no check that the integration branch has protection rules requiring the pipeline to pass.
Observed behavior
- Agent created a CI pipeline. Code was merged and PRs landed without waiting for the pipeline because no branch protection was configured.
Desired behavior
- After a pipeline is created (or detected in the session), the agent checks whether the integration branch has protection rules that require the pipeline.
- If protection is missing, the agent suggests adding it.
Acceptance criteria
- Pipeline creation flow verifies branch protection and prompts the user when it is absent.
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 locating the pipeline creation flow and how the integration branch is identified. Check how branch protection rules and required pipeline status are queried, then verify the flow prompts the user when protection is absent after a pipeline is created or detected. Done means the acceptance criterion is covered by tests or a reproducible verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100