actions Archives - The GitHub Blog
https://github.blog/changelog/label/actions/
Updates, ideas, and inspiration from GitHub to help developers build and design software.Mon, 18 Sep 2023 16:05:29 +0000en-US
hourly
1 https://wordpress.org/?v=6.3.1https://github.blog/wp-content/uploads/2019/01/cropped-github-favicon-512.png?fit=32%2C32actions Archives - The GitHub Blog
https://github.blog/changelog/label/actions/
3232153214340Migrate Bamboo and Bitbucket Pipeline to GitHub Actions
https://github.blog/changelog/2023-09-18-migrate-bamboo-and-bitbucket-pipeline-to-github-actions
Mon, 18 Sep 2023 16:00:05 +0000https://github.blog/changelog/2023-09-18-migrate-bamboo-and-bitbucket-pipeline-to-github-actionsMigrate Bamboo and Bitbucket Pipeline to GitHub Actions
]]>GitHub Actions Importer now supports migrations from Bitbucket, Bamboo Server, and Bamboo Data Center. Companies using those tools can plan, test, and automate the migration of pipelines to GitHub Actions more easily than ever before.
GitHub Actions Importer is available via the GitHub CLI or IssueOps. To get started, please visit our docs. For questions and feedback, check out the GitHub Actions Importer community.
]]>GitHub-hosted runners now support up to 1000 concurrent jobs for our 4 – 64 vCPU runners, enhancing their capability to handle large-scale CI/CD workloads.
Our runners are designed to automatically scale to meet your needs. The concurrency limit feature allows users to specify the maximum number of jobs that can run simultaneously to execute Actions workflows. Previously capped at 250, we've made backend improvements to now support a maximum of 1000 concurrent jobs for runners within the 4-64 vCPU range for Windows and Linux operating systems.
Enterprise or organization administrators can set this concurrency limit under the Auto-scaling setting. GitHub-hosted runners with 4 or more vCPUs are available on both the GitHub Team and Enterprise plans.
If you have any feedback to help improve this experience, be sure to post it on our GitHub Community Discussion.
]]>We have implemented a fix so that GITHUB_REF and the github.ref context value return a fully-formed ref (e.g – refs/heads/main) when a workflow is triggered as a result of a pull request being merged. This change only impacts a small subset of workflows that trigger as a result of a pull request closing after being merged and that make use of GITHUB_REF or github.ref.
Previously, GITHUB_REF and github.ref were incorrectly returning a shortened ref (e.g. – main). These should always return a fully-formed ref regardless of the scenario.
Please visit our documentation for more details about using Actions context and variables.
]]>GitHub-hosted larger runners now support dual IP ranges when configured with Static IPs for the GitHub Enterprise Cloud plan.
Static IP enables Enterprise Cloud customers to choose whether a static IP address range will be assigned to their larger runner instances. This provides a fixed IP address range that can be added to your allow list for access to internal systems and can be used in conjunction with GitHub’s IP allow list to enable hosted actions runners and IP allow listing at the same time.
With dual IP ranges, larger runner instances will now receive two IP ranges instead of a single range. This enables runners to scale beyond the previously existing 500 concurrency limit. Additionally, the two IP ranges are created in different geographical locations, providing resiliency against regional outages.
Getting started
For newly created larger runner instances with the Static IP feature, 2 IP ranges will be assigned by default going forward and no additional action is required.
For existing larger runner instances that have Static IP configured:
GitHub will assign an additional IP range(s) that admins can view by heading to their existing static IP enabled larger runners.
Admins will have 30 days to update their existing firewalls or internal IP allowlists with the new IP ranges before GitHub starts utilizing the new ranges for the runners.
Admins will also receive an email guiding them to take the necessary steps for their existing static IP enabled larger runners to continue to function as they switch to the dual IP range functionality.
You can learn more about the Static IP feature by heading over to documentation. If you have any feedback to help improve this experience, be sure to post it on our GitHub Community Discussion.
]]>73993Update to Actions usage in Enterprise Managed User namespace repositories
https://github.blog/changelog/2023-08-29-update-to-actions-usage-in-enterprise-managed-user-namespace-repositories
Tue, 29 Aug 2023 20:48:07 +0000https://github.blog/changelog/2023-08-29-update-to-actions-usage-in-enterprise-managed-user-namespace-repositoriesUpdate to Actions usage in Enterprise Managed User namespace repositories
]]>Enterprise Managed User namespace repositories were previously able to use GitHub-hosted Actions runners outside of the owning enterprise's entitlements. This was not an intentional configuration. Today we have disabled the ability for EMU user namespace repositories to use GitHub-hosted runners.
For customers using inner source workflows we recommend forking from an organization owned repository into your user namespace. You may then open a pull request back to the upstream repository and actions workflows will run as usual within the context of that organization and enterprise.
]]>GitHub Actions asks customers to review their network allow list for self-hosted runners according to the requirements in our documentation.
Network access to GitHub's *.actions.githubusercontent.com is essential for the self-hosted runners. Requiring wildcard access allows GitHub Actions to be flexible moving forward as we improve the service. Customers that do not allow wildcard access risk having interruptions in their GitHub Actions usage as we start enforcing this requirement on September 12, 2023. Please reach out to the customer support if you have limitations with configuring wildcard access in the on-premises firewall solution.
]]>73909Repository Actions Runners List
https://github.blog/changelog/2023-08-21-repository-actions-runners-list
Mon, 21 Aug 2023 17:43:01 +0000https://github.blog/changelog/2023-08-21-repository-actions-runners-listRepository Actions Runners List
]]>With the Repository Actions Runners List, you can now view all available runners in the Actions tab of a repository. This feature is now in public beta and will be gradually released in the upcoming weeks.
For some benefits of using the Repository Actions Runners List:
Visibility across all GitHub Actions runners: Users with repo:write access can now view runner options without needing to rely on internal documentation or contacting a Repo admin or an Organization owner for runner label names.
Faster access to runner labels: Quickly view and copy labels for all runners, making it straightforward to identify the type of runner you need and use it in a workflow.
To access the Repository Actions Runners List:
Navigate to the main page of the repository.
Click the “Actions” tab under your repository name.
Under the “Management” section in the left sidebar, click on “Runners”.
Explore the available runners for the repository and copy runner labels as needed.
Note: Enterprise and Organization owners can also create new runners from this page from the “New runner” button.
This feature is available to users with:
Free and Pro Personal Accounts
Free Organizations
Paid Organizations on the Team and GitHub Enterprise Cloud plans
Note: This feature is not currently available to users in Organizations on the GitHub Enterprise Server and Legacy plans, or Enterprise Managed Users.
]]>73778Actions runs triggered from tags or forks with the same name as a protected branch will now be blocked
https://github.blog/changelog/2023-08-10-actions-runs-triggered-from-tags-or-forks-with-the-same-name-as-a-protected-branch-will-now-be-blocked
Thu, 10 Aug 2023 19:23:40 +0000https://github.blog/changelog/2023-08-10-actions-runs-triggered-from-tags-or-forks-with-the-same-name-as-a-protected-branch-will-now-be-blockedActions Runs triggered from tags or forks with the same name as a protected branch will now be blocked
]]>GitHub environments can be configured with deployment branch policies to allow-list the branches that can deploy to them.
We are now security hardening these branch policies further by blocking runs triggered from forks with branches that match the protected branch name. We are also preventing tags with the same name as a protected branch from deploying to the environments with branch policies around protected branches.
Learn more about configuring environments with deployment protection rules to set up rigorous and streamlined guardrails for your deployments.
]]>Support for migrating Jenkins Scripted Pipelines to GitHub Actions is now available as a private beta! If you use Scripted Pipelines in your Jenkins instances, you can now automate the migration of your pipelines to GitHub Actions using GitHub Actions Importer.
]]>73555GitHub Actions: Required Workflows will move to Repository Rules
https://github.blog/changelog/2023-08-02-github-actions-required-workflows-will-move-to-repository-rules
Wed, 02 Aug 2023 21:23:14 +0000https://github.blog/changelog/2023-08-02-github-actions-required-workflows-will-move-to-repository-rulesGitHub Actions: Required Workflows will move to Repository Rules
]]>We will be moving the private beta of required workflows on GitHub Actions to Repository Rules to give organization administrators a powerful way to protect their repositories with added feature benefits including unified configuration, dry running workflow rules, branch targeting, and a consistent UI experience.
Starting September 20th, 2023, users can configure their workflows using rulesets in order to run and pass in selected repositories before merging their code. On October 18th, users will no longer be able to access Actions Required Workflows and must use rulesets in its place.
How does this impact beta users of Actions Required Workflows?
Existing Actions Required Workflows private beta users will continue to have access until October 18th, 2023, allowing them time to adapt to the forthcoming changes. During this transitional period, users will maintain their existing workflows without disruption. This ensures that organizations can smoothly navigate the migration process, avoiding any abrupt disruptions to their current code merging practices. Here’s a quick overview of the events leading up to the move.
For GHEC customers
Leading up to October 18th:
GitHub will attempt to automatically migrate any existing Required Workflows to Rulesets for customers.
Any workflow files that did not successfully migrate will need to be manually migrated by code owners.
After October 18th:
The ability to require a workflow to pass before merging code will only be available on GitHub Enterprise plans via Repository Rules
Organization Rulesets will enable administrators to define, configure, and manage all workflows required to pass before merging code in repositories.
The feature formally known as Actions Required Workflows will no longer be accessible and users will be directed to Rulesets.
For GHES customers by version
GHES 3.8 and 3.9 will not be impacted until their next upgrade
GHES 3.10 and 3.11 will not be impacted if Actions Required Workflows are already in use
GHES 3.12 Requiring a workflow to run and pass before merging will be only be available vis Repository Rulesets
To learn more about how Repository Rules can help control how people can interact with branches, visit our documentation.
<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
The post Migrate Bamboo and Bitbucket Pipeline to GitHub Actions appeared first on The GitHub Blog.
]]>GitHub Actions Importer is available via the GitHub CLI or IssueOps. To get started, please visit our docs. For questions and feedback, check out the GitHub Actions Importer community.
The post Migrate Bamboo and Bitbucket Pipeline to GitHub Actions appeared first on The GitHub Blog.
]]>The post Increased Concurrency Limit for GitHub-Hosted Runners appeared first on The GitHub Blog.
]]>Our runners are designed to automatically scale to meet your needs. The concurrency limit feature allows users to specify the maximum number of jobs that can run simultaneously to execute Actions workflows. Previously capped at 250, we've made backend improvements to now support a maximum of 1000 concurrent jobs for runners within the 4-64 vCPU range for Windows and Linux operating systems.
Enterprise or organization administrators can set this concurrency limit under the Auto-scaling setting. GitHub-hosted runners with 4 or more vCPUs are available on both the GitHub Team and Enterprise plans.
If you have any feedback to help improve this experience, be sure to post it on our GitHub Community Discussion.
The post Increased Concurrency Limit for GitHub-Hosted Runners appeared first on The GitHub Blog.
]]>The post GitHub Actions – Updates to GITHUB_REF and github.ref appeared first on The GitHub Blog.
]]>GITHUB_REFand thegithub.refcontext value return a fully-formed ref (e.g –refs/heads/main) when a workflow is triggered as a result of a pull request being merged. This change only impacts a small subset of workflows that trigger as a result of a pull request closing after being merged and that make use ofGITHUB_REForgithub.ref.Previously,
GITHUB_REFandgithub.refwere incorrectly returning a shortened ref (e.g. –main). These should always return a fully-formed ref regardless of the scenario.Please visit our documentation for more details about using Actions context and variables.
For questions, visit the GitHub Actions community.
To see what's next for Actions, visit our public roadmap.
The post GitHub Actions – Updates to GITHUB_REF and github.ref appeared first on The GitHub Blog.
]]>The post Dual Static IP ranges for GitHub-hosted Larger runners appeared first on The GitHub Blog.
]]>Static IP enables Enterprise Cloud customers to choose whether a static IP address range will be assigned to their larger runner instances. This provides a fixed IP address range that can be added to your allow list for access to internal systems and can be used in conjunction with GitHub’s IP allow list to enable hosted actions runners and IP allow listing at the same time.
With dual IP ranges, larger runner instances will now receive two IP ranges instead of a single range. This enables runners to scale beyond the previously existing 500 concurrency limit. Additionally, the two IP ranges are created in different geographical locations, providing resiliency against regional outages.
Getting started
For newly created larger runner instances with the Static IP feature, 2 IP ranges will be assigned by default going forward and no additional action is required.
For existing larger runner instances that have Static IP configured:
You can learn more about the Static IP feature by heading over to documentation. If you have any feedback to help improve this experience, be sure to post it on our GitHub Community Discussion.
The post Dual Static IP ranges for GitHub-hosted Larger runners appeared first on The GitHub Blog.
]]>The post Update to Actions usage in Enterprise Managed User namespace repositories appeared first on The GitHub Blog.
]]>For customers using inner source workflows we recommend forking from an organization owned repository into your user namespace. You may then open a pull request back to the upstream repository and actions workflows will run as usual within the context of that organization and enterprise.
Learn more about enabling private repositories to run actions workflows from forks.
The post Update to Actions usage in Enterprise Managed User namespace repositories appeared first on The GitHub Blog.
]]>The post GitHub Actions: Review network access settings for the self-hosted runners appeared first on The GitHub Blog.
]]>Network access to GitHub's
*.actions.githubusercontent.comis essential for the self-hosted runners. Requiring wildcard access allows GitHub Actions to be flexible moving forward as we improve the service. Customers that do not allow wildcard access risk having interruptions in their GitHub Actions usage as we start enforcing this requirement on September 12, 2023. Please reach out to the customer support if you have limitations with configuring wildcard access in the on-premises firewall solution.Learn more about GitHub Actions self-hosted runners.
For questions, visit the GitHub Actions community.
To see what's next for Actions, visit our public roadmap.
The post GitHub Actions: Review network access settings for the self-hosted runners appeared first on The GitHub Blog.
]]>The post Repository Actions Runners List appeared first on The GitHub Blog.
]]>The runner types listed include Standard GitHub-hosted, Larger GitHub-hosted (for faster builds), Self-hosted, and Scale-sets.
For some benefits of using the Repository Actions Runners List:
repo:writeaccess can now view runner options without needing to rely on internal documentation or contacting a Repo admin or an Organization owner for runner label names.To access the Repository Actions Runners List:
Note: Enterprise and Organization owners can also create new runners from this page from the “New runner” button.
This feature is available to users with:
Note: This feature is not currently available to users in Organizations on the GitHub Enterprise Server and Legacy plans, or Enterprise Managed Users.
If you have any feedback to help improve this experience, be sure to post it on our GitHub Community Discussion.
The post Repository Actions Runners List appeared first on The GitHub Blog.
]]>The post Actions runs triggered from tags or forks with the same name as a protected branch will now be blocked appeared first on The GitHub Blog.
]]>We are now security hardening these branch policies further by blocking runs triggered from forks with branches that match the protected branch name. We are also preventing tags with the same name as a protected branch from deploying to the environments with branch policies around protected branches.
Learn more about configuring environments with deployment protection rules to set up rigorous and streamlined guardrails for your deployments.
For questions, visit the GitHub Actions community.
To see what's next for Actions, visit our public roadmap.
The post Actions runs triggered from tags or forks with the same name as a protected branch will now be blocked appeared first on The GitHub Blog.
]]>The post [Private Beta] Jenkins Scripted Pipeline Migrations appeared first on The GitHub Blog.
]]>To get started, please reach out to your GitHub account manager or contact our sales team! For questions and feedback about the private beta, please visit the GitHub Actions Importer community.
The post [Private Beta] Jenkins Scripted Pipeline Migrations appeared first on The GitHub Blog.
]]>The post GitHub Actions: Required Workflows will move to Repository Rules appeared first on The GitHub Blog.
]]>Starting September 20th, 2023, users can configure their workflows using rulesets in order to run and pass in selected repositories before merging their code. On October 18th, users will no longer be able to access Actions Required Workflows and must use rulesets in its place.
How does this impact beta users of Actions Required Workflows?
Existing Actions Required Workflows private beta users will continue to have access until October 18th, 2023, allowing them time to adapt to the forthcoming changes. During this transitional period, users will maintain their existing workflows without disruption. This ensures that organizations can smoothly navigate the migration process, avoiding any abrupt disruptions to their current code merging practices. Here’s a quick overview of the events leading up to the move.
For GHEC customers
Leading up to October 18th:
After October 18th:
For GHES customers by version
To learn more about how Repository Rules can help control how people can interact with branches, visit our documentation.
The post GitHub Actions: Required Workflows will move to Repository Rules appeared first on The GitHub Blog.
]]>