-
Notifications
You must be signed in to change notification settings - Fork 75
Create a melodic-devel branch and pull from my fork #186
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
Comments
I've preferred to keep everything in one branch since there I don't think there are any differences between kinetic/melodic/etc that would actually impact Any thoughts @chfritz ? |
We should definitely update the node versions we test too |
I don't think it's critical to test against kinetic, but one thing I'll say for sure: the fact that the main branch is called |
Sounds good to me. I'll rename to |
i will pull request then, if you like. Maybe waiting on #185 to be merged |
nvm, i see #189 already does the trick |
I added a melodic-devel branch here and changed
.travis.yml
accordingly. Please consider opening a melodic-devel branch and pull from my repo.The text was updated successfully, but these errors were encountered: