Video on how to fix pull request process with automation

Pull Request visualization

Modern pull request visualization means that the change and the impact of the change are visualized in graphical form. Visualization provides a fast overview of the change and additional information comparing the textual code-diff. Pull request visualization doesn’t only save time on reviews but reveals architectural issues before the merge.

Save time and increase quality by automated pull request visualization!

Pull requests are a great process to review code changes in an agile way. But even with good test automation in place, actually reviewing the change is still a time-consuming task and could overwhelm the reviewers.

Please see the video below illustrating how you can improve your pull request process by adding analytics and automated visualization as part of the process!

  • Save time in the review process -> get faster merges
  • Find architectural issues -> reduce technical debt, increase the quality
  • See the real impact of the change (Not seen by traditional method), to find issues _before_ the merge!

Visual pull request analysis is supported in Bitbucket, VSTS/TFS (Azure DevOps), GitHub and GitLab environments.

Return of Investment

In the agile software development process, every developer creates around 20 pull request review events every month. (1-2 pull requests per week and 3 reviews for each of them). For 100 developers that’s over 2000 times a month! Automated analysis and clear dependency and impact visualization save time in each of them. Automatic detection of architecture violations prevents to create spaghetti-code in small steps. Better architecture creates huge savings in code-maintainability and re-use. Transparency due visual overview in each pull requests is a good way to improve the best practices. 

How to evaluate pull request visualization with own code?

If you are using git version-control with cloud access versions of GitHub, Bitbucket, GitLab or VSTS/TFS (Azure DevOps) taking Softagram automated pull request visualization is requiring few simple steps. First login to Softagram Cloud and then add your repo’s under analysis!

If you want to run the system on-premises, then the development for your own virtual server requires to contact us. Please leave your information below and we get back to you with the steps to go forward. 

 

Trackbacks & Pings

  • Stop loosing new developers time, change the code from text to visuals. :

    […] Automated pull request visualizations will dramatically speed the review time and give fast understanding of the changes also for new developers. Activating Softagram to create clear visualization of the changes before the merge allows also the creator of pull request to see the impact of the change in visual format, as well as see if the change would violate any archtiecture rules with un-wanted new dependencies. More about that unique use case in this post. […]

    5 months ago
  • What do you gain with automated analytics for each pull request? :

    […] Softagram Impact Report uses multiple KPIs to rate the pull request risk level and shows the most critical files to focus the attention. It finds the hidden impact of the change, as well as e.g. un_wanted new dependencies or missing unit tests. Based on the rules it can automatically create an issue for the contributor to be fixed before the merge. See a video example of the Softagram impact report. […]

    4 months ago
  • Top findings from GitHub Octoverse 2018 :

    […] the last 12 months, that is over 300 000 per working day! (Amazing amount of review events, where Softagram could give a hand! […]

    1 month ago

Leave a Reply Text

Your email address will not be published. Required fields are marked *