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
[feature request] Use Github Actions instead of (along with) Travis #21
Comments
|
Thanks @fyodorio that's a really good idea. I haven't had the time to dig into them though and don't have time right now for that. Would be happy to review a PR if you feel like raising one 👍 |
|
@maxime1992, put me as an assignee? I will send a PR until the next day. |
|
Hi guys :) Thanks @PauloGoncalvesBH for offering your help 🙏. I'd be super glad to get a PR but before that I'd like to make sure we are all talking about the same thing here? I'd say we can keep Travis as it was a one time setup here for the publishing of the NPM module. @fyodorio is it what you had in mind too? @PauloGoncalvesBH is it what you were thinking of? Because I think such a contribution would fit better in the template here: https://github.com/maxime1992/dev.to rather than this repo |
|
Also, @beeman wrote an article few days ago: https://dev.to/beeman/automate-your-dev-posts-using-github-actions-4hp3 in case that's of any help :) |
|
Update here, not 100% related but a little bit. Travis setup wasn't working anymore on this repo so I migrated to Github Actions to build/publish this project. We should indeed provide an example to have this as the default to publish blog posts as well instead of Travis 👍 @PauloGoncalvesBH are you still interested in making a PR for this? |
|
I've done it in the template repo though https://github.com/maxime1992/dev.to/blob/master/.github/workflows/main.yml ✔️ |
Using Github Actions instead of Travis (or as an option to choose) would provide for free (and presumably faster) CI workflow with private repos
The text was updated successfully, but these errors were encountered: