7 messages
Discussions related to GitHub Actions
S
Sean Turner4 months ago(edited)
Hey all, any idea what's the best way to enable a Github Application to approve PRs?
Usecase:
Python library versions are published in upstream repo
Downstream repos trigger a GHA that add the new version and open a PR that needs to be approved (gets put in merge queue automatically)
So I want to automate the approval of the PR (which is perfect as we're happy as long as automated tests are passing)
I've learned through doing that a GHA (authenticating to Github with the GHA Token) in one run cannot approve a PR created by another GHA with the same auth paradigm
I've also learned that while a Github Application can approve a PR (I impersonated the App for testing purposes), branch protection rules mark this approval as an "un-approved reviewer"
In the repo I tested (downstream consumer of the libray) we don't actually have a
I guess looking at your repos I see a number of commits are by https://github.com/actions-user?
Usecase:
Python library versions are published in upstream repo
Downstream repos trigger a GHA that add the new version and open a PR that needs to be approved (gets put in merge queue automatically)
So I want to automate the approval of the PR (which is perfect as we're happy as long as automated tests are passing)
I've learned through doing that a GHA (authenticating to Github with the GHA Token) in one run cannot approve a PR created by another GHA with the same auth paradigm
I've also learned that while a Github Application can approve a PR (I impersonated the App for testing purposes), branch protection rules mark this approval as an "un-approved reviewer"
In the repo I tested (downstream consumer of the libray) we don't actually have a
.github/CODEOWNERS defined. So I suppose by default this is determined by the Collaborators and teams repository-level settings.I guess looking at your repos I see a number of commits are by https://github.com/actions-user?
rss4 months ago(edited)
Actions Runner Controller release 0.13.0
Actions Runner Controller (ARC) release 0.13.0 is now available and provides improvements in storage, networking, platform, and metrics. Enable container hooks to remove storage limitations ARC now supports container lifecycle…
The post Actions Runner Controller release 0.13.0 appeared first on The GitHub Blog.
Actions Runner Controller (ARC) release 0.13.0 is now available and provides improvements in storage, networking, platform, and metrics. Enable container hooks to remove storage limitations ARC now supports container lifecycle…
The post Actions Runner Controller release 0.13.0 appeared first on The GitHub Blog.
A
Alek4 months ago(edited)
Hello Team! Still new to Atmos, so please excuse me if the question is basic.
Having made a bunch of changes to our EKS addon placement, I'm hitting some issues executing
My workflow was straight forward - I made a PR with changes to EKS addon versions and configuration, which generated a matrix of successful plans across all my regions in
Something I considered was to delete the old planfiles from the S3 bucket manually and retry, but I wanted to check here if there's something I am missing.
Component:
Having made a bunch of changes to our EKS addon placement, I'm hitting some issues executing
apply using the official Atmos GitHub Actions: plan files have differencesMy workflow was straight forward - I made a PR with changes to EKS addon versions and configuration, which generated a matrix of successful plans across all my regions in
prod. Then, I merged the PR, with auto-apply label on it. Still, the apply to my stacks fail - but it does not fail reliably. Some matrix jobs pass, and changes are applied, but others fail with this error.Something I considered was to delete the old planfiles from the S3 bucket manually and retry, but I wanted to check here if there's something I am missing.
Component:
<http://github.com/cloudposse-terraform-components/aws-eks-cluster.git//src?ref=v1.535.0|github.com/cloudposse-terraform-components/aws-eks-cluster.git//src?ref=v1.535.0> (found no related changes in the EKS module between mine and latest component versions).rss4 months ago(edited)
1 vCPU Linux runner now available in GitHub Actions in public preview
GitHub Actions 1 vCPU Linux runners are now in public preview. Customers looking to run lightweight operations can take advantage of these lower cost runners. These runners are optimized for…
The post 1 vCPU Linux runner now available in GitHub Actions in public preview appeared first on The GitHub Blog.
GitHub Actions 1 vCPU Linux runners are now in public preview. Customers looking to run lightweight operations can take advantage of these lower cost runners. These runners are optimized for…
The post 1 vCPU Linux runner now available in GitHub Actions in public preview appeared first on The GitHub Blog.
rss4 months ago(edited)
Custom images for GitHub-hosted runners are now available in public preview
Custom images for GitHub-hosted runners are now available in public preview. This feature allows you to start with a GitHub-curated base image and build your own virtual machine image tailored…
The post Custom images for GitHub-hosted runners are now available in public preview appeared first on The GitHub Blog.
Custom images for GitHub-hosted runners are now available in public preview. This feature allows you to start with a GitHub-curated base image and build your own virtual machine image tailored…
The post Custom images for GitHub-hosted runners are now available in public preview appeared first on The GitHub Blog.
rss4 months ago(edited)
Copilot coding agent now supports self-hosted runners
You can now configure Copilot coding agents’s development environment to run in your own infrastructure using self-hosted GitHub Actions runners managed by Actions Runner Controller (ARC). With this setup, you…
The post Copilot coding agent now supports self-hosted runners appeared first on The GitHub Blog.
You can now configure Copilot coding agents’s development environment to run in your own infrastructure using self-hosted GitHub Actions runners managed by Actions Runner Controller (ARC). With this setup, you…
The post Copilot coding agent now supports self-hosted runners appeared first on The GitHub Blog.
T
toka4 months ago
Hey, I'm using https://github.com/cloudposse/github-action-atmos-affected-stacks and I got stuck.
I have created a PR which introduces 3 stacks and number of components, and was able to produce GH Job matrix just fine. Then PR got merged into main branch, and I expect to execute Atmos Terraform Apply from the main branch after merging.
The thing is, PR was left open for couple of days and the Matrix artifact expired.
I cannot get to re-run it in a way that would produce the same matrix without changing inputs or settings in the components themselves - I cannot afford that since my goal is to make Terraform Import during Atmos Terraform Apply without any changes in infra.
Triggering again against master brach results in no changed being detected.
Any ideas how to get around that?
I have created a PR which introduces 3 stacks and number of components, and was able to produce GH Job matrix just fine. Then PR got merged into main branch, and I expect to execute Atmos Terraform Apply from the main branch after merging.
The thing is, PR was left open for couple of days and the Matrix artifact expired.
I cannot get to re-run it in a way that would produce the same matrix without changing inputs or settings in the components themselves - I cannot afford that since my goal is to make Terraform Import during Atmos Terraform Apply without any changes in infra.
Triggering again against master brach results in no changed being detected.
Any ideas how to get around that?