In new beta, however repos created prior nonetheless use older actions

Code to Cloud GitHub Actions
#1

I’ve noticed I’m within the equal bucket as some other customers who have commented here — I’ve been introduced to the brand new Actions beta, however any repos I even have that existed prior to that turnover are nonetheless attempting to use the older Action style. Is there some thing I can do to turn the ones older repos over?

It can be something uniquely bizarre to my account of service— I’m in an company that also simply added to the brand new beta, however it seems that the older repos in that agency made the transition first-class.from https://github.com/freeCodeCamp/freeCodeCamp

here’s an example

job.<job_id>.branches

An example of usage would be:

jobs:
  Publish:
    name: Publish Container
    runs-on: ubuntu-latest
    branches:
    - master

jobs:
  Publish:
    name: Run long workflow not needed for master for some reason
    runs-on: ubuntu-latest
    branches:
    - !master 

 I am trying to run my e2e check on a github actions but i simply realised that your linux virtual system does not support virtualization is that something you would possibly encompass later?

1 Like
#2

Hi @loshteri9 ,

Thank you for being here!  Do you mean in your repos created prior still use older actions and accept syntax like below?

jobs:
  Publish:
    name: Publish Container
    runs-on: ubuntu-latest
    branches:
    - master

Have you tried to fix the code with new actions and syntax , and does it work? I checked on my older repo, all works fine.

The repos can be archived, changed to private, or deleted from repo setting(https://github.com/{org}/{repo}/settings), I’m not sure what do you mean by turn it over. Could you please share your repo/yaml file?

Regarding the virtualization feature, it’s recommended to raise a ticket here for confirmation, github engineer will take a review and answer.

1 Like