Code scanning support for 3rd party CI/CD

You can now run CodeQL analysis in any CI/CD setup and upload the results to GitHub code scanning.

Previously, the code scanning beta required users to run their CodeQL analysis using GitHub Actions. Now, for organizations who wish to adopt code scanning without using Actions, we have released the new CodeQL runner. The runner makes it easy to run CodeQL analysis from any CI/CD system and upload the results to GitHub for display as code scanning alerts.

Learn more about running code scanning in your CI system

You can now use images from private registries in job and service containers.

Job and Service containers in GitHub Actions allow you to containerize your CI environment and make databases, caches, or other services available to your tests. Previously those containers had to come from a public container registry which limited the usefulness for some customers. Additionally, we had numerous requests from the GitHub community forums for private registry support.

Here’s an example of using private images from Docker Hub and GitHub Container Registry:

jobs:
  build:
    container:
      image: octocat/ci-image:latest
      credentials:
        username: mona
        password: ${{ secrets.docker_hub_password}}
    services:
      db:
        image:  ghcr.io/octocat/testdb:latest
        credentials:
          username: ${{ github.repository_owner }}
          password: ${{ secrets.ghcr_password }}

For questions, visit the GitHub Actions community forum.

To see what’s next for GitHub Actions, visit our public roadmap.

See more