Latest articles from Axolo

Axolo will now send reminders to sleeping pull requests, change pull request titles upon their status, send weekly analytics and forward checks messages to Slack! Learn more here.

At Axolo, we think that two characteristics are most important for handling pull requests: attention and speed. A great code review should be done within a few hours after a request and be thoroughly processed.

Code review is one of the most important practices engineers should have. Your code will always need to be reviewed, and you will always need to review your coworkers' code. If you approach code reviews as a learning process, everyone wins.

In Part II of our Pull Request Guide, we will dive into the processes of opening to merging a pull request and the best advices and integrations to master your code reviews.

Pull requests are an opportunity for a software developer to notify team members (or open-source project maintainers) that a feature or fix, developed on a different branch is ready. Learn more about them in our study.

This product update will cover GitHub/Slack OAuth, /lgtm command, edit/delete propagation accross your tools, how we handle pull request checks and the Sentry integration.

Engineering Manager Interview is a series of interviews launched by Axolo. Discover story behind Front creation, how they scaled their engineering team, and secured their technology.

This product update will cover: selecting status of Action or Deployment, code reviewing time slots for deep work sessions, mention in Github, request for changes / approve from Slack and self-onboarding in Axolo.

We decided to launch a new kind of referral program: the Donut 🍩 Ambassador program. It's your lucky day! What is it? For every successful company that installs and uses Axolo for more than two weeks, we will send your whole tech team free donuts. 🎉

Building Axolo we've interviewed 100+ CTO // head of engineering and we’ve asked them what they considered good practice. Here is the list: