Home Products December Product Update πŸš€

December Product Update πŸš€




Hi there πŸ‘‹,

With 2022 behind us, we can now welcome 2023 and focus on making it an incredible year! Your friends here at Codacy wish you a Happy New Year, full of health, happiness, and a beautiful codebase! πŸŽ‰

Let’s kick off this year with some exciting product updates!

[Quality] Better visibility on Coverage errors

Our team has been working hard on enhancing our UI to allow you to better troubleshoot any issues with Coverage.

After successfully setting up Coverage, you can now see a warning message on the Pull Request detail page when Codacy Quality can’t calculate your PR metrics. The message includes a link to the Coverage tab in your repository settings, where you can test and validate your coverage setup.

This new message lets you know there’s an error and shows you how to fix it.

Coverage Pull Request Issue
Coverage Pull Request – Warming Message

[Pulse] Bitbucket integration is now live!

We’re very excited to announce that Codacy Pulse now supports Bitbucket integration! You can collect changes and deployment data from Bitbucket repositories into Pulse’s Accelerate dashboard.

This new integration is going to be released in stages:

  • βœ… Stage 1: We show you the Accelerate dashboard metrics using merged Pull Requests to detect deployment automatically.
  • ➑️ Stage 2: We’ll soon be able to import historical data and backfill the dashboards automatically – we’re almost there!

Meanwhile, check out our docs if you have questions about the Bitbucket integration.

Codacy Pulse Bitbucket Installing
Codacy Pulse – Bitbucket integration

[Pulse] Track the impact of changes with Notes

Changes in your organization’s internal or external environment can impact your software delivery process. For example, changes in the team structure, adoption of new working processes, or major events affecting the system stability might impact your teams’ performance.

That’s why we’re introducing Notes to Codacy Pulse. Notes are an easy way to annotate actions or events that took place on a specific date and correlate them with Engineering productivity metrics. All the Notes will be visible on your organization’s dashboards.

How can your Engineering team use Notes?

  • To keep track of your continuous improvement journey, visualize actions and their impact.
  • In a retrospective meeting, you can review recent actions and evaluate if they meet the expected outcome.
  • Engineering Managers can use Notes in their 1:1s to share with team members the impact of their work.
Pulse Notes card
Codacy Pulse – Notes card

Careers at Codacy: We’re Hiring πŸ€©

We’re hiring for our Engineering (Frontend), Product, 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.

Interesting reads 

How to reduce cyclomatic complexity in 5 practical ways πŸ§‘β€πŸ’» 

Cyclomatic complexity is the number of possible execution paths inside a given piece of code. Having a too high cyclomatic complexity can mean you have problems with your codebase. So let’s see how you can reduce it. Read here β†’ 

“60 Practices For Quality Engineering: Skills” by QE Unit πŸ€“

Do you want to know what you need to start with Quality at Speed software? Quality Engineering will help you get started. Its implementation depends on the 5 domains of MAMOS: Methods, Architecture, Management & Culture, Organization, and Skills. Let’s see Skills β†’

“How to keep up with CI/CD best practices” by Valerie Silverthorne πŸ™Œ

“Continuous integration and continuous delivery (CI/CD) are at the heart of any successful DevOps practice. Teams wanting to achieve modern software development must keep up with CI/CD best practices. Here’s what you need to know to make sure your team is on the right track.” Keep reading here β†’

9 Clean Code principles you can apply NOW in your code” by Justin Graysen 🫧

Developers spend a lot of time working on existing code. Since time is of the essence in most software development teams, it’s essential to use best practices to have clean code and make everyone’s work easier. How? Here are 9 principles β†’


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 πŸ™Œ πŸ‘«

Top Community Users December 2022

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 πŸ’ͺ

See what’s next β†’

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! β›΅


Please enter your comment!
Please enter your name here

Subscribe to our newsletter

To be updated with all the latest news, offers and special announcements.

Recent posts

How does code quality fit into your CI/CD pipeline?

Continuous Integration and Continuous Deployment (CI/CD) are key for organizations wanting to deliver software at scale. CI/CD allows developers to automate...

How Stim uses Codacy to achieve high-quality code

We spoke with Tobias SjΓΆsten, Head of Software Engineering at Stim, about how Codacy helps them guarantee code quality and standardization...

6 things developers should do to ship more secure code

Writing better, more secure source code is fundamental to prevent potential exploits and attacks that could undermine your software applications. However,...

Best practices for security code reviews

In today's interconnected world, where data breaches and cyber threats are increasingly common, one of your top priorities should be to...

April Product Update πŸš€

Hi there πŸ‘‹ It's been a whirlwind month, and we have big news to share: