Use GitHub action to verify/lint/validate/generate documentation tables instead of Travis #274
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please review this pull request urgently, this must be the next one to be merged before any other
Apparently there are security issues with the use of Travis and public logs, which lead to the exposure of the Travis token and the subsequent iteration of the public repositories for which you received emails end of last week.
GitHub revoked all my tokens due to this, which means currently Travis does not check/lint/validate/generate anything currently.
I changed the workflow to use GitHub Actions instead of Travis, made it clearer what is done by separating it into several steps and configured it to run on pull_requests and pushed to the branches "master" and "changes_for_v1.1".