All Posts

We introduced GitHub Proxy configuration for enterprises, enhanced impersonation security, provided LGTM tips in PR channels, and automated PR channel closure. Sign-in and Slack message formatting have been improved. Enhancements include better customer success notifications, updated onboarding messages, refined analytics, proactive feedback collection, and post-plan update emails. Fixes addressed enterprise team channel management, weekend reminders, sign-in without organizations, and unarchiving PR channels.

We will focus on the integration of GitLab, a popular tool for version control, with Microsoft Teams, a widely-used platform for team communication. Currently, there is a notable gap in the market: GitLab has not yet developed an official integration for Microsoft Teams.

A detailed guide on managing Stacked PRs for efficient code reviews, featuring popular tools like Ghstack, Git Town, Sapling, Spr, and Graphite.

We updated features with admin access requests, improved Slack and email notifications, personalized stand-up alerts, usage-based free plan, and subgroup onboarding for GitLab. Security enhancements include VPN-secured API and admin panel. Improvements cover login issues, notification updates, and GitLab bot identification. Fixed a bug related to new user welcome emails.

Axolo offers a unique approach to PR management by creating a notification channel per team and a dedicated Slack channel for each PR, inviting only the relevant team members.

Understanding the cost structure of GitHub Enterprise is crucial for businesses that are scaling their development operations. GitHub Enterprise offers a range of features designed to meet the needs of larger organizations, including enhanced security and more robust collaboration options. This article aims to provide a comprehensive guide to GitHub Enterprise Server pricing, breaking down the various factors that contribute to the overall cost.

This blog post explores the intricacies of pull request management, offering best practices and tool recommendations like Axolo and Mergify to streamline the process.

Are you an engineering manager, VP of engineering or CTO of a growing tech company? If yes, stay with us, if no, you can still stay with us but I don't know why you would. In the dynamic world of tech, growth is inevitable, if you're good, or sometimes lucky. But as your projects expand and demands surge, how do you ensure that your engineering team scales effectively?

Code reviews are a big part of any tech team's day-to-day. They help us make sure we're writing the best code possible and catch any bugs early. But let's be honest, they can also be tiring and take up a lot of time. Plus, sometimes pull requests sit there waiting for a review, becoming 'stale' and holding up the whole development process. In this article, we'll dig into the common challenges of code reviews and how they can lead to delays and fatigue.

I think it would be quire nice if we could configure which pull request events we can subscribe to. Something like:pulls:all - Opened, closed and merged PRs,pulls:new - Opened PRs,pulls:closed - Closed PRs