-
Notifications
You must be signed in to change notification settings - Fork 378
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
Travis CI and pull requests #122
Comments
Maybe we should specify / clarify a branching policy as well? |
Ideally, travis-ci should build new releases automatically. That would take care of #127 |
|
@vincenthage, it looks like you already applied those fixes in the travis branch. Where you able to fix Coverity? It looks like it is still pointing to the old URL. |
* Update Coverity Settings to current project URL * Update status badges for ci * Update README.rst Bugs: #122
* Update Coverity Settings to current project URL * Update status badges for ci * Update README.rst Bugs: #122
As a new contributor, I am finding a hard time figuring out what the tests actually do; the names aren't very descriptive. Perhaps we should include a comment in each test summarizing what the test does? |
Hi,
Travis CI has been renabled on this repos;
it should make PR-merging easier, as it looks like most of them are frozen.
And by that I mean PRs that are probably working and only missing throughout testing on multiple environments.
So now when introducing a new feature or a bug fix, we should also add a test along it
(or is-it too much and it would slow down PR merging even more?).
Any commit/merge on master, and update on pull requests will trigger a run,
but the existing pull requests won't be run until they are updated in some way
so we will have to manually update them (either with a commit or by closing/opening them).
If you have any comment about the current state of PRoot and how to improve it,
don't mind leaving a message here.
Cheers,
Vincent
The text was updated successfully, but these errors were encountered: