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.
Organization owners can now disable publication of GitHub Pages sites from repositories in the organization. Disabling GitHub Pages for the organization will prevent members from creating new Pages sites but will not unpublish existing sites.
You can learn more about this new setting in our documentation.
Logs for GitHub Actions have gotten a significant update. Some major enhancements and new features include:
Check out our detailed blog post on the new Logs Experience for more information.
For questions please visit the GitHub Actions community forum
To see what's next for GitHub Actions, visit our public roadmap