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.
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.
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.
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:
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.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
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?
Which would then get stuck into our settings.py programmatically?