How does Devin fit into my existing SDLC?
Understanding Devin’s integration with software development lifecycle workflows
Overview
Devin contributes to existing codebases and repositories by creating Pull Requests (PRs) containing its suggested code changes. Devin is subject to the exact same branch/SDLC protections as any human engineer. Human engineers in the Loop review PRs created by Devin before choosing whether or not to merge the code changes.
Devin can also use its tools like the shell and the browser to take actions. If Devin is to take a constructive action via those tools (for example, using the shell to make an API call), a Human engineer will need to 1) provide credentials to Devin via the in-built Secrets Manager and 2) instruct Devin to do so. Devin will not automatically take actions with its tools unless instructed to do so by the Human engineer.
Key Integration Points
Pull Request Workflow
- Devin creates PRs with suggested code changes
- All standard branch protection rules apply to Devin
- Human engineers review and approve PRs before merging
- Same code review process as any Human team member
Tool Usage Authorization
- Credentials must be provided via Devin Secrets Manager
- No automatic actions without human approval
- Full audit trail of all actions taken