about summary refs log tree commit diff stats
path: root/.github/workflows
Commit message (Collapse)AuthorAgeFilesLines
* Remove trailing whitespacea13460542021-08-251-1/+1
|
* Actions: Add on pull_request againtoonn2021-07-243-0/+12
| | | | | | | | | | | | | | | My testing was flawed. The status checks seemed to work fine because the builds were triggered on push in the same repo. But this doesn't work across repos. So GH Actions having run to completion on someone's fork doesn't give us the status checks we need. Therefore we want to run our Actions on PRs too, that way they're run from the ranger repo as well and the status checks should actually be informative. One possible improvement is that we could duplicate the workflows we want to run on PRs, that way we can drop all the things that don't really matter for status checks from the version matrices. Otoh that means we have pretty much duplicated workflows we need to keep in sync. Thank you for your lack of abstractions, GH Actions 🙄
* Actions: Check whether on_pullrequest is necessarytoonn2021-07-203-12/+0
|
* Actions: Reduce tested versions to oldest and newesttoonn2021-07-203-4/+4
|
* Actions: Fix Python and Pypy paths filterstoonn2021-07-202-3/+3
|
* Actions: Drop on_pullrequest from Pypytoonn2021-07-201-6/+2
| | | | | We need to get it passing first before we can make it a useful status check on PRs.
* Actions: Fix pylint and Pypy paths filtertoonn2021-07-202-4/+4
|
* Actions: Drop Pypy from pylint and add pylint to Pypytoonn2021-07-202-2/+2
|
* Actions: Update shellcheck required actionstoonn2021-07-201-3/+1
|
* Actions: Refine Pypy versions and titletoonn2021-07-201-2/+2
|
* Actions: Separate pypy tests because they failtoonn2021-07-203-2/+36
|
* Actions: Update, incorporate and splittoonn2021-07-203-41/+38
| | | | | | Update the required actions. Incorporate doctest and manpage_completion test in the test action and separate pylint because it doesn't work with as many python versions.
* Actions: Drop 3.5 from linting because of old pylinttoonn2021-07-201-1/+1
|
* Actions: Set TERM=dumb to avoid tput warningstoonn2021-07-202-0/+4
|
* Actions: Try to fix missing terminfotoonn2021-07-201-0/+1
|
* Actions: Add on pull_request to get status checkstoonn2021-07-203-3/+11
| | | | | | This should enable the pylint, pytest, flake8 and shellcheck lints to run when PRs are opened and have them act as status checks so PRs aren't merged without them passing.
* Fix shellcheck version commenttoonn2021-01-051-1/+1
|
* Fix shellcheck download urltoonn2021-01-051-1/+1
|
* Document expected failure of GH Actiontoonn2020-07-051-1/+1
| | | | | | | Github Actions don't support some of our tests, due to `ncurses`. This Action fails intentionally so it might get fixed once we figure it out. If we invert the failure condition to "make CI green" we might forget about it.
* Clarify excluded tests for github workflowtoonn2020-07-052-3/+3
| | | | | Add pytest to the failing workflow because otherwise it's not run with python 2.7.
* Prepare for Pylint transition from versions <2toonn2020-07-053-34/+4
|
* Seperate doctests and pyteststoonn2019-09-242-2/+32
| | | | | | Doctests are interfering with CI because curses can't find the terminfo database. This'll require looking into but for now we'll run the doctests seperately and expect failure. Same thing for pytests.
* Segregate python 3.7 workflowtoonn2019-09-181-0/+30
| | | | | | By seperating the python 3.7 workflow we can keep an eye on changed linting errors for the newer pylint. Without cancelling the actions for our current setup.
* Drop py3.7toonn2019-09-181-1/+1
| | | | | Temporarily drop python 3.7 from the workflow because it's not compatible with `pylint<2`.
* Add GitHub Actions citoonn2019-09-032-0/+52
Run our python tests and shellcheck in seperate workflows only when relevant files are changed, respectively python files or `scope.sh`. This tests with one extra version of python, 3.7. GitHub's version of shellcheck seems to be missing a few flags. So we download the latest stable version, 0.7.0 currently.