To store secrets in github go to settings/secret in your repo and add them there, f.i. APIKEY. You can access them (in github actions) with ${{ secrets.APIKEY}}
Thank you, I will check it out. I read something about GhitHub Actions but it was an older article and it was saying that the solution wasn't yet stable.
I'm living in 🇱🇺Luxembourg,🇪🇺Europe.
Speaking 💬FR/EN/ES & few words of LU.
Working as 💻UX Designer, Product Development #ergonomie #UI . My
🔏GPG is E6BAE5E6 but also keybase.io/thibault
Location
Luxembourg, Luxembourg
Education
Licence Pro Metier du web @ UPVM Metz
Work
Innovation Evangelist at Smile Open Source Technologies
The solution is definitely stable now. They iterated a few times and change completely the specification language from what it was at first. I'm using it to build and deploy a few applications (even recombine multiple application into 1 deployment for a website host on S3, but could have been GitHub pages, it's just my employer want control over the destination). So using secrets definitely work 👍🏼
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To store secrets in github go to settings/secret in your repo and add them there, f.i. APIKEY. You can access them (in github actions) with
${{ secrets.APIKEY}}Thank you, I will check it out. I read something about GhitHub Actions but it was an older article and it was saying that the solution wasn't yet stable.
The solution is definitely stable now. They iterated a few times and change completely the specification language from what it was at first. I'm using it to build and deploy a few applications (even recombine multiple application into 1 deployment for a website host on S3, but could have been GitHub pages, it's just my employer want control over the destination). So using secrets definitely work 👍🏼