Action needed by GitHub Connect customers using GHES 3.1 and older to adopt new authentication token format updates
Upgrade to GHES 3.2 or newer by June 3rd to continue using GitHub Connect.
When you want to create a workflow in the Actions tab of your repository, the recommendations are now based on an analysis of repo content.
Today, we’re announcing improvements to the GitHub Actions “New Workflow” experience. Now, when you want to create an Actions workflow in the Actions tab of your repository, the recommendations will be based on an analysis of repository content. We have also added search and filters to help you find the right workflow that matches your unique requirements.
The workflow recommendations are based on repository analysis that detects elements, such as programming language, build tools, frameworks, and package managers. For example, if a repository contains a Node.js application that has been containerized, then the repository analysis will prioritize showing you both container and Node related workflows.
We have also extended recommendations to the deployment category. For example, if a repository contains a Dockerfile, we’ll suggest a workflow that builds these containers and deploys them to a container-compatible cloud service. This enables our cloud partners to contribute workflows for each of their services and helps them recommend the right workflows to end users based on the language and framework used in the repository code.
Additionally, we have added the ability to filter by categories, plus search capabilities on the catalog of Actions workflows, to help you find the right workflow that matches your requirements faster.
GitHub has a catalog of workflows that are recommended based on the code in your repository. You can learn more about GitHub Actions workflows in our documentation. For any questions or suggestions, join the discussion here.