Pull Requests for Infrastructure Access

Making frequent changes to cloud applications running in production is the de-facto standard. To minimize errors, engineers use CI/CD automation, techniques like code reviews, green-blue deployments and others. Git pull requests often serve as a foundational component for triggering code reviews, Slack notifications, and subsequent automation such as testing and deployments. This automated process enforces peer reviews and creates enough visibility to minimize human error.


GitHub Security Code Scanning: Secure your open source dependencies

We are happy to announce Snyk Open Source support for GitHub Security Code Scanning, enabling you to automatically scan your open source dependencies for security vulnerabilities and license issues, as well as view results directly from within GitHub’s Security tab! A key ingredient of Snyk’s developer-first approach is integrating Snyk’s security data into the exact same processes that developers are using, whether this is within a developer’s IDE or a Git-based workflow.

Create and Run Jobs with a Cypress Test in Github Actions

In this video, you will learn to set up two simple jobs with GitHub Actions and Saucectl to create a pipeline that builds and tests an example web app, as well as runs a test on Sauce Labs' virtual machines using Testrunner Toolkit and Sauce Control. Starting from a project set up in a previous tutorial, learn to add jobs to a github workflow .yml file. Use Actions to start a Sauce Connect Proxy Tunnel, install saucectl, and use it to run an automated test using Cypress.

Deploy a Jekyll site to AWS S3 using GitHub Actions

In this tutorial, I will show you how to build and deploy a Jekyll static site to AWS S3 + Cloudfront using GitHub Actions. At PagerTree we use GitHub Actions to automate the building and deploying of our marketing site These days, if you have to do anything manually more than a couple of times, you should probably be automating it. GitHub Actions make it easy to automate software workflows.


GitHub CI/CD tutorial: Setting up continuous integration

Continuous integration (CI) involves the test automation of feature branches before they are merged to the main Git branch in a project. This ensures that a codebase does not get updated with changes that could break something. Continuous Delivery (CD), on the other hand, builds upon CI by automating releases of these branches or the main branch. This allows small incremental updates that reach your users faster, in line with Agile software development philosophy.


Nightfall for GitHub, Now with Real-Time Data Loss Prevention

We are excited to announce that Nightfall DLP for GitHub now has two plans available: Pro and Enterprise. Both plans allow you to discover, classify and protect sensitive information in any GitHub organization by actively scanning your codebase for secrets, credentials, PII, and other business-critical data to notify you of data policy violations. The Enterprise plan provides the additional ability to scan the commit history of any repo within your GitHub org.


Github vs Gitlab: An Impartial Guide

In our latest tools guide, we wanted to gather insights from a number of real users of these two giants in the Git & version control space to help you decide between using Github or Gitlab for your latest software development project. “GitHub is a common and easy-to-use website to host code in a way that's shareable with a large number of people”, states Melanie, Content Director at KitelyTech.


Application security automation for GitHub repositories with Snyk

Snyk provides a wide array of integrations and a pretty comprehensive API to enable you to deploy Snyk across the SDLC and monitor all the code your organization is developing. Of course – this is not always simple. At scale, ensuring Snyk is monitoring all your repositories becomes more challenging. As you grow, more code is added in the shape of new repositories. Not only that, existing repositories keep on changing.

Using SQL Clone with Githooks & Branch Policies in Azure DevOps

Switching branches quickly and testing Pull Request code when working on database changes is no easy thing, but fear not! Join Chris Unwin in this video to find out how you can set up SQL Clone to allow developers to preserve changes when switching branches, and how teams can review code against a live DB, rather than relying on the raw code in version control.