Code Release Workflow

This Code Release & Quality Check workflow template helps development and product teams stay on the same page during production releases. By automating the logging of production pushes and notifying relevant team members, this workflow ensures smooth communication and prompt quality checks. It enables you to keep the product team informed of releases while automatically checking the code’s performance post-release, ensuring your product meets quality standards with minimal oversight.

Key Steps:

1. Configure the Trigger Settings:
   • When This Event Happens: Use the “Starts when an external activity is tracked” option and integrate it with your preferred version control tool (e.g., GitHub, GitLab) via API. Set it to trigger every time a new code push to production is recorded.
   • Customization Tips: Configure the trigger to include specific branch names (e.g., main, production) to avoid false alerts from non-production pushes.
2. Send the Code Release to a Channel or DMs:
   • Send Notification Messages: Use “Send a chat message” to notify the product and QA teams when a push is logged. This message can include release details like commit messages, branch name, and release author. It can be sent either to DMs of specific people and to public or private channels.
3. Additional Settings for Workflow Optimization:
   • Use AI to Communicate Efficiently: You can configure “Generate content with AI based on a given input” before you send the message to format the output and provide insights or potential next steps for the team.
   • Send Consolidated Release Summary: Use “Send the consolidated report of a Check-in” to provide a weekly or monthly summary of all releases and their statuses to the team, creating a valuable historical record.

Best Practices & Tips:

• Use Real-Time Notifications: Real-time notifications help the product team stay aligned with new releases and quickly prepare for any customer-impacting updates.
• Customize Release Messages: Use variables to auto-fill each notification with key details about the release (e.g., branch, release manager) to make updates clear and actionable.
• Establish Release Summaries: Weekly release summaries give everyone, especially non-technical stakeholders, an overview of recent updates and overall quality trends.
• Integrate with QA Reporting Tools: To maintain high code quality, set up automated QA tools to run tests post-deployment, and feed these results into DailyBot for immediate visibility. This enables the product team to respond promptly if any major issue arises.

This workflow streamlines the code release process, bringing together development, product, and QA efforts into one cohesive flow. With clear notifications, quality tracking, and accessible insights, your team can focus on delivering high-quality updates while staying informed of any potential issues in production.