Goedkeuringsworkflows
Stel multi-level goedkeuringsketens in voor deployments.
Approval workflows ensure that changes go through proper review before being deployed to production. Configure who needs to approve what, and maintain quality control across your team.
Why Use Approval Workflows?
Approval workflows help teams:
- Maintain Quality — Ensure code is reviewed before deployment
- Reduce Risk — Catch issues before they reach production
- Stay Compliant — Meet audit and compliance requirements
- Knowledge Sharing — Keep team members informed of changes
Approval Workflow Overview
[Screenshot placeholder]
Setting Up Workflows
To configure approval workflows for your project:
- Go to your project settings
- Navigate to the "Workflows" tab
- Click "Add Approval Rule"
- Define conditions and required approvers
Approval Rules
You can create rules based on various conditions:
- All Changes — Require approval for every deployment
- Production Only — Only require approval for production deployments
- Specific Paths — Require approval for changes to critical files
- By Ticket Type — Different rules for features vs bugfixes
💡Required Approvers
You can specify the minimum number of approvals required, or require approval from specific team members or roles.
Approving Changes
When a change requires your approval:
- You'll receive a notification
- Review the changes in the preview environment
- Check the AI-generated code diff
- Approve or request changes with feedback
✨Quick Approve
For trusted team members, you can enable "Quick Approve" which allows their changes to be deployed after a single approval instead of the usual requirement.
Bypassing Approvals
In emergency situations, administrators can bypass approval workflows. All bypasses are logged for audit purposes.
Was dit artikel nuttig?