Although in the new beta, new repos have the old actions #25890
-
I’ve successfully setup the new actions for one repo, but now that i want to do it for another repo, i don’t see a way to “upgrade” it or “enable” the new actions. I honestly can’t remember how i got the first repo enabled, but i would like to be able to use it with multiple repos |
Beta Was this translation helpful? Give feedback.
Replies: 17 comments
-
When I create a new repo, the actions is already upgraded to the new system. Have you tried creating the .github/workflows/<something>.yml file to see if it works? |
Beta Was this translation helpful? Give feedback.
-
I have not tried that yet. good point though :slight_smile: i’ll give that a shot |
Beta Was this translation helpful? Give feedback.
-
no luck…it’s a public repo, but making it private doesn’t seem to make a difference… I was able to upgrade another repo that had an old workflow file, so it seems to still be available at least… |
Beta Was this translation helpful? Give feedback.
-
Hi Dennis, I could upgrade your entire account. Sound good? |
Beta Was this translation helpful? Give feedback.
-
that would be awesome! thanks @mscoutermarsh |
Beta Was this translation helpful? Give feedback.
-
Done. try now. 😎 |
Beta Was this translation helpful? Give feedback.
-
success!! thank you! off to building docker images now :D |
Beta Was this translation helpful? Give feedback.
-
@mscoutermarsh I’m having the exact same issue. I have been enrolled in both the old and new betas and have a new repo that seems to insist on only using the old workflow syntax. Adding a new style workflow file https://github.com/softprops/rust-bin/blob/master/.github/workflows/main.yml in place doesn’t seem to be detected by the actions tab. For some extra context in other repos there’s usually a prompt (that I don’t need) to opt into the new syntax. This repo didn’t have it which makes this repo unique. If possible can I only be enrolled in the new syntax beta to avoid new repos using the old syntax. |
Beta Was this translation helpful? Give feedback.
-
@softprops Just enabled for your entire account. Give it a try now 😀 |
Beta Was this translation helpful? Give feedback.
-
Same issue for me, I was only able to upgrade a single repo - I have quite a number of them and I’d like to switch them all from webhooks to actions 😄 |
Beta Was this translation helpful? Give feedback.
-
Also having the same issue. I would like to use the new actions in my other repos as well. |
Beta Was this translation helpful? Give feedback.
-
@mscoutermarsh you are the best! Thanks for the fast turn around. |
Beta Was this translation helpful? Give feedback.
-
seems like I am having the same problem |
Beta Was this translation helpful? Give feedback.
-
I believe I’m seeing the same thing as well. New repos appear to have new workflows, but all of my old ones do not. An organization I’m in also just got access to the beta, and even its older repos are using the new style, so perhaps I’m in a weird limbo too! 😬 |
Beta Was this translation helpful? Give feedback.
-
+1 any chance of having my whole @chrisns account done so my new repos can use new actions? |
Beta Was this translation helpful? Give feedback.
-
If this happens to anyone else, you can get around it by creating an HCL syntax workflow. Then you’ll see the option to upgrade. You need an old-style one and then it will just offer it and you can move forward without waiting for staff to upgrade you manually. |
Beta Was this translation helpful? Give feedback.
Hi Dennis,
I could upgrade your entire account. Sound good?