Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Suggest: enable Travis CI again #48

Open
richelbilderbeek opened this issue Jul 13, 2020 · 1 comment
Open

Suggest: enable Travis CI again #48

richelbilderbeek opened this issue Jul 13, 2020 · 1 comment
Assignees
@pratikunterwegs

Comments

@richelbilderbeek
Copy link
Collaborator

Hi @pratikunterwegs,

As I described here, Travis CI is innocent in putting many files in the root of the project. Due to a misunderstanding, Travis CI was de-activated, which is reasonable would Travis CI indeed be the culprit.

As Travis CI is innocent, however, I suggest to enable it once more, as a Travis CI build badge is an honest indicator of quality.

I would have done so myself, but sadly I do not have the right access rights.

Thanks!
richelbilderbeek pushed a commit that referenced this issue Jul 13, 2020
Blindly merge 'richel' to 'master', due to disabled Travis CI (see #48)
3aa4ed5
@richelbilderbeek richelbilderbeek mentioned this issue Jul 13, 2020
Open
richelbilderbeek pushed a commit that referenced this issue Jul 14, 2020
Merge to master blindy, as Travis CI is not yet enabled (Issue at #48)
0e343ac
@richelbilderbeek
Copy link
Collaborator Author

As to be clear, I also volunteer to maintain the Travis CI file, .travis.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pratikunterwegs pratikunterwegs

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richelbilderbeek @pratikunterwegs