Closed adamrdavid closed 4 years ago
I will take it look it at, but first I need to take a detailed look at Travis before activating it.
Now with github actions I think it would be better to use that. examples: https://github.com/bugcrowd/vrt-ruby/actions https://github.com/bugcrowd/vulnerability-rating-taxonomy/runs/383957128
I also thought about Actions but didn’t have time to take a closer look. Maybe will do in the next weeks can’t promise though.
Okay 👍 I'm going to close this out as not relevant anymore.
Proposed changes
Get Travis CI working so that we can have those nifty commit status markers and a build status badge on the readme. This might also allow us to remove the check boxes for passing tests in the pull request template
Examples:
Types of changes
What types of changes does your code introduce to CvssSuite?
None of the below, only a github/CI change
Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR.Further comments
This will require someone with an owner role to enable Travis CI for the repo here: https://travis-ci.org/siemens/cvss-suite