Closed ryanmrichard closed 2 years ago
Evidently only repository collaborators are able to add workflows, and I am not one of them. I have looked through Actions though and it seems relatively simple to do everything here, there's Actions specifically for each of those tasks for Python projects, ex:
Linting: https://github.com/marketplace/actions/python-linting Unit tests: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions Code Coverage: https://github.com/codecov/codecov-action
ReadTheDocs will have to be separate as there doesn't appear to be a dedicated module for triggering builds, but since they have webhooks support it shouldn't be an issue for us.
I wouldn't worry about this for the moment. While it would be nice to have things running through GitHub, our present setup accomplishes most of this already.
@AutonomicPerfectionist are you sure you can't make a PR with a .github/workflows/test.yaml
file? Since Travis seems to have stopped working for whatever reason, it would be great to minimally switch unit testing over to GitHub to get that working again.
Yes I can make such a pull request, I believe my previous statement was referencing the Actions tab in Github instead of manually adding the files
Gotcha. You're not missing much by not having access to that tab, basically: are actions allowed?, how long should the artifacts be kept?, and what are GITHUB_TOKEN
's permissions?
Implemented in #40
Minimally I'd like the following to be automated as part of CI:
Exactly how the above get accomplished, is open for discussion. I think it's going to make sense to leverage GitHub's actions as much as possible, but I can see things like documentation working better through Read The Docs.