This helps ensure your code flows smoothly from development to production. If you mention a pull request, Bitbucket will show you a summary of the salient details, highlighting the outstanding work-missing approvals, failed builds, and uncompleted tasks-required to get it merged. Context, when you need itĪlongside notifications, Bitbucket provides contextual information from your repositories, if and when you need it. The notification is updated with the latest status, so the rest of the team stays in the loop with what’s happening with your builds and PRs. Complete tasks from your channelīitbucket’s new chat notifications are more than just informative – you can now perform key Bitbucket tasks without leaving your channel. With a click on the notification, any member of the team (with appropriate permissions) can create a pull request from a newly pushed branch, re-run a failed build pipeline, or reply to a pull request comment.īut our favorite new feature has to be the ability to “nudge” reviewers, to gently remind your teammates that you needed that code reviewed yesterday. You no longer have to passive-aggressively click the approve/unapprove button to ping your team about it. However we try to be a bit smarter about less critical notifications: you’ll be notified about pushes, merges, and builds only for your primary branch-typically master or default, depending on whether you’re using Git or Mercurial.īitbucket detects if you’re using a Gitflow branching strategy, and will automatically notify your team when a new feature branch is created. And these are just the defaults! All notifications are fine-grained, configurable, and able to be bound to specific branches or branch patterns. Different notifications from the same repository can be configured to be sent to different channels-for example, you might send pull request events to #dev and builds or deployments to #ops-so you can tailor each repository subscription to suit your team’s needs. Wait, “an out-of-the-box customized experience” – how does that make sense? Well, when you create a chat subscription, Bitbucket performs an automated analysis of your repository and configures notifications tailored to your usage patterns.īy default, your team will be notified about important events like pull request activity and commit comments across the entire repository. Smarter, by defaultĭebates have sparked weighing the benefits of real-time communication and productivity costs. Being constantly inundated with notifications-both automated and human-can take their toll on any team trying to focus. By analyzing the usage of Bitbucket’s existing HipChat, Slack, and Stride integrations, we’ve carefully balanced the default notifications to provide an out-of-the-box experience customized for your team. The bot is available today for Slack, and is coming soon to Atlassian Stride and other leading chat platforms. Bitbucket Cloud’s new chatbot features a wide range of notification types, plenty of interactivity, and some smart configuration features that will supercharge your team’s development workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |