You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is a good idea! There are a number of services that are free for open source projects, including Travis CI and Circle CI. We should set up one of these to run the tests automatically on every push and every pull request.
The text was updated successfully, but these errors were encountered:
One thing that could be an issue is that most of CI services assume that the Rails app is in the root of the repo. In our case, it's in the MYR_rails directory.
@takluyver is there any historical reason why it was in a sub-directory? Would you be open to move it to the top directory?
That was how it was when I inherited it; I think at some point the plan may have been to have the rails app in one directory and an Android frontend in another. Conceptually, I quite like having a separate directory for the tracker hardware details, but if it's going to be a problem, that can be a subfolder inside the rails app.
I'd suggest having a brief look for options to test a rails app that's not the root of the repo. If it's easy to say "look in this directory", we can do that. If not, or if there are other downsides, we can make it the repo root.
Is a good idea! There are a number of services that are free for open source projects, including Travis CI and Circle CI. We should set up one of these to run the tests automatically on every push and every pull request.
The text was updated successfully, but these errors were encountered: