Welcome to the GitHub Actions board

This board is for the discussion of GitHub Actions, now with support for Continuous Integration and Deployment. Discussion of how they work and any questions or feedback you have about the feature are welcome here. Share your tips, tricks, and interesting actions or workflows.

GitHub Actions is currently in limited beta now GA

 

What does this mean?

Since GitHub Actions is currently in beta, this means that things might change without warning, documentation may be incorrect and need updating, and things might unexpectedly break. We do not recommend building production-level services on GitHub Actions until this feature is out of beta.

If you do notice that something is broken or that some documentation is incorrect, please let us know. We will not be able to give you an estimation on when these things will be fixed, but we will add this information to our queue to be addressed.

How can I get into the beta?

To gain access to the GitHub Actions beta, please sign up for the waitlist. As this feature is much anticipated, the waitlist is rather long and it might take some time before you are approved.  Posting in this forum will not allow you quicker access into the beta.

Additional Resources

In addition to the information you find in the forum, here are some links to documentation and other resources we think you might find helpful:

11 Likes

Hi,

As you mentioned,

>> _ To gain access to the GitHub Actions beta, please sign up for the waitlist. As this feature is much anticipated, the waitlist is rather long and it might take some time before you are approved. _ >>

Is there an estimate on the amount of time it takes to gain access? I am learning GitHub Actions recenly, and I need to gain the access to test some workflows created by myself. As we known, it is helpful to test while learning. But now, we only can read the documentation and not test.

I will be grateful for any suggestions that can help me.

Hi @brightran

Thank you for reaching out!  We are rolling it out as fast as we can.  You’ll see more news on that timeline here as well: Please give some guestimate on a wait time

@nyahbhinghiprincess, Actions is now enabled on my account. Every thing work fine currently.

Thanks for your response.

1 Like

So for a django application we would deploy to a pre-production server and a production server.

How would you handle different secrets for test and production? Just different names and a trigger script?

e.g. AWS_CREDENTIALS_PROD

AWS_CREDENTIALS_TEST

Which would then get stuck into our settings.py programmatically?

Thanks

I think this post should be updated now that Actions is out of beta.

I recommend updating this post at least daily.

Hey, My Action for github action hackathon got rejected saying that it is not a usable action,

Please solve this issue ASAP,So that i can submit urgently.

Link to my repo-https://github.com/Potential17/Twitter-retweet-bot

1 Like

@that-patthanks for the infomation. will use GA in my next repo.

@brightran wrote:

Hi,

 

As you mentioned,

>> _ To gain access to the please sign up for the waitlist. As this feature is much anticipated, the waitlist is rather long and it might take some time before you are approved. _ >>

Is there an estimate on the amount of time it takes to gain access? I am learning GitHub Actions recenly, and I need to gain the access to test some workflows created by myself. As we known, it is helpful to test while learning. But now, we only can read the documentation and not test.

I will be grateful for any suggestions that can help me.

_ How do I add actions to GitHub??? and What is GitHub secret??? _