Operations | Monitoring | ITSM | DevOps | Cloud

For most organizations, GitHub is mission critical. Your GitHub repositories likely also contain some of your organization’s most sensitive data. GitHub provides tools to help you protect and govern this data, with tools such as audit logs, code scanning alerts, and secret scanning alerts. However, analyzing these logs and alerts through GitHub’s UI can be challenging. For example, looking for trends in your code scanning alerts over time through GitHub’s UI is just not possible.

Welcome to the last day of our first Checkly Launch Week! We already talked about security, our new Playwright test runner and alert enhancements. Today, I’m delighted to announce that GitHub Sync is going into general availability (GA)! This post goes into the following topics.

Like I’ve mentioned in my last blog post, we use GitLab pipelines for packaging. We have a lot of software, like Icinga, Icingaweb and its various modules, which we want to build across multiple different operating systems. This results in a huge number of jobs and pipelines, doing very similar stuff. We have a lot of code repetition, and this is bad – code repetition means higher code maintenance , and it invites bugs.

Bug bounty programs set up by software companies that incentivize white-hat hackers, developers, and engineers alike to identify and report bugs in a specified software. Many large tech companies like Google, Microsoft, Facebook, Atlassian, and others host these programs to ensure that their code is secure.

Nobody likes resolving merge/rebase/cherry-pick conflicts. I also don’t, but I’ve found a scheme how to reduce the built-in headache. In this post I’m going to share my findings as well as practical examples.

Git is a version control system (VCS) that allows you to track the development of a project over time. At the time of Git’s inception in 2005, developers had to use the command line interface (CLI) to manage Git. Learning and using the command line however is often an extremely difficult task for many developers and in some cases represents a significant barrier of entry for those seeking to leverage the power of Git. Enter the graphical user interface (GUI), also referred to as a Git Client.

Git hooks are an accommodating solution for organizations that seek to implement consistent policies and procedures across their teams. First and foremost, they enable teams to run custom scripts according to certain Git operations. Building automation into your Git client helps remove the possibility of human error and improves workflows with little effort. Here we will explore how Husky works with Git hooks in JS projects. First, let’s start with the basics.