-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Out of the box GitHub Actions support #525
Comments
@buschtoens I would be glad to work with you on this. We have a lot we need to do to modernize this project. I've been slowly chipping away at it. |
I got it working in ember-intl/ember-intl#1425, without the use of I was trying to base my setup on @NullVoxPopuli's setup in Anyhow, the The only annoying thing is that the credentials are set via Unless a really nice |
It would be nice if we had a CI agnostic solution, so things could be built and deployed on Travis, GitHub Actions, Circle etc. but if it is easier to just support GitHub Actions, I do think that is the best choice to lock down on. |
Definitely, CI-agnostic would be best - I agree. We don't necessarily need to drop Ideally we'd have a nice GitHub Actions plugin for |
@buschtoens certainly open to suggestions. I think one defined path is okay here, and removing dependencies is always nice, however what about the case where a user wants to deploy adhoc? |
Looks like there is another issue for this too #437 |
👋 just wanted to say that I've been updating ember-jsqr a bit, and the GH Workflow I had for addon-docs didn't work anymore (used old / no-longer-existing / insecure GH Action API). I removed that bit and now only docs updates on the master branch are deploying (no versioned docs). I'm investigating a bit still |
Turns out I had a |
nope, that wasn't it. It seems my tagged workflow isn't triggering at all 🤔 |
It would be great to get out of the box support for GitHub Actions or at least a go-to guide.
The text was updated successfully, but these errors were encountered: