Action branch names with / broken in 2.273.4?
See original GitHub issueAs of today if our actions come from a branch on a repo with /
in the branch name it fails with errors like this:
Unable to resolve action `Brightspace/third-party-actions@actions/checkout`, repository not found
We do this a lot because we mirror third-party-actions into branches in a central repo in our org (more context available in the README).
We’re seeing it fail on v2.273.4 runners, at least.
I see a lot of .Split( '/' )
in here, but I haven’t finished investigating: https://github.com/actions/runner/compare/v2.273.3...v2.273.4#diff-488a6cefa4a643b9314f32898b46937eR51
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:9 (1 by maintainers)
Top Results From Across the Web
How to get the current branch within Github Actions?
I'm building Docker images with Github Actions and want to tag images with the branch name. I found the GITHUB_REF variable, but it...
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
Here are 7 tricks with github actions that changed my life (or at least my CI/CD ... name: Pull Request on: pull_request: branches:...
Read more >Branches | GitLab
As your project grows, your team creates more branches, preferably by following branch naming patterns. Each branch represents a set of changes, ...
Read more >Running GitHub Actions CI/CD triggers on specific branches
You want certain events to run on specific branches. You adjust the YAML to include branch names to only run CI checks on...
Read more >Can't find the right GitHub action? Create it! | by Efi Shtain
When working with preview environments in the cloud, I tend to create environments based on the current branch name as a unique subdomain....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry for the trouble, we identified a bug in a change we rolled out to the Actions Service that caused this and rolled it back. The runner is fine to continue using as-is. Thanks again for reporting this and let us know if you continue to see the issue!
👋🏾 Hello there from the Actions team, thanks for reporting this! I will take a look and see what I can find.