February 2013 Product Update 🚀
Hi there 👋,
Here are a few updates from February with very exciting news, so keep on reading!
[Quality] Improving product experience
Our team has been working hard to improve your experience with the product to make it more enjoyable. Our product squads have been focusing on, among others:
- Providing a more streamlined user management experience. In some Enterprise plans, we now automatically add to the organization new people that commit to your private repos and analyze their commits.
- Updating the versions of the tools. For example, ESList was updated to version 8.34.0, and we added support for the ESLint plugins @remix-run/eslint-config and eslint-config-qiwi.
- Features improvements, mainly the multiple organization coding standards. All the invisible work will become visible to you soon!
[Pulse] Historical data for semantic version tags
Codacy Pulse now supports historical data for semantic version tags in the GitHub integration!
As a new user creating a new organization, you can choose how to detect deployments: from Pull Requests or semantic version tags. With semantic version tags, you can import data for up to a year (instead of 3 months), allowing you to see metrics without waiting for them to accumulate!
If you’re an existing Pulse user, a historical import will not be triggered when you change your integration settings. Contact us via the in-app support chat if you’d like a historical import for your organization.
Check out our docs if you have questions about semantic version tags.
[Pulse] Automatic incident detection
We know that incidents are the hardest event type to ingest into Codacy Pulse, and the manual integration via PagerDuty or the API can be painful. As a result, the Accelerate dashboard is incomplete for most users, without the Time to recover and the Change failure rate metrics.
To help with this, we’re introducing automatic incident detection whenever you revert a Pull Request. We know which PR is being reverted, so we can infer how long the Incident took to calculate the Time to recover.
Pulse can also detect Incidents from arbitrary PRs. You can configure a prefix identifying a branch name or PR title to match the naming convention of what is a rollback or hotfix in your workflow.
If you’re already collecting Incidents, this feature will be disabled by default, but you can opt-in anytime. Head to our docs or contact us via the in-app chat if you have any questions.
[Next Webinar] Leading Your Team to Engineering Excellence
Join our guest speaker, Steve Berczuk, Lead Software Engineer at Riva Health, and Stuart James, Engineering Manager at Codacy, in discussing how to help your team achieve engineering excellence.
[Community] We want your feedback!
In January 2021, we launched the Codacy Community, a place for experienced and novice engineers and developers to support, challenge, and inspire one another.
However, the Community is not as active as we hoped. So would love your feedback on how we can make the Codacy Community more useful to you! Head over to our community and cast your vote.
Careers at Codacy: We’re Hiring 🤩
We’re hiring for our Engineering (Frontend), Sales, Customer Success, and Design Teams. All remote positions – join us from anywhere in Europe and help us do awesome things! Check our current openings.
How Mobile Premier League (MPL) uses Codacy to improve development efficiency 🤩
Learn how Mobile Premier League (MPL) uses Codacy to improve development efficiency and achieve engineering excellence. See also how they aim to use Quality in combination with Pulse. Read here →
“Undefensive Code Review” by Matthew Spence 🤝
Code reviews are not personal, but sometimes they seem that way, and the author becomes defensive because it’s like they are under review, not the code. To change this, we need to build an environment where people don’t feel the need to be defensive. Learn more →
“How to Read Technical Books Effectively” by Recep İnanç 📚
“Reading a technical book is a lot different than reading a novel. That is why we need a different strategy to get the best out of technical books. I have been in the pursuit of a good reading technique for years now. I have tried to follow different approaches and finally, I was able to find a way that works for me well.” Keep reading here →
We are more almost 600 members in our community! 🚀
Your support and feedback are very important to us, and we look forward to keep growing and learning with you. Thank you all 🙌 👫
Give feedback on our Roadmap
We’d like to continue sharing our roadmap with you ✨ You can see what’s in progress and what’s up next. You can also submit an idea/feature request and vote on what is most important! Your feedback matters 💪
If you think this content is relevant to you, we would be extremely happy to send it over to you every single month. Feel free to subscribe below, and welcome on board! ⛵