ranger - mirror of ranger - a simple, vim-like file manager

	Commit message (Collapse)	Author	Age	Files	Lines
*	GHActions: Refrain from installing PyLint for tests	toonn	2022-06-13	1	-1/+3
\| \| \| \| \| \|	Not all versions of Python we test with support installing the PyLint version we need and the tests don't require PyLint anyway, so no need to install any version of PyLint at all.
*	GHActions: Rerun PyLint when requirements.txt changes	toonn	2022-06-10	1	-0/+2
\|
*	Actions: Pytests no longer compatible with Python <3.6	toonn	2022-02-05	2	-3/+3
\| \| \| \| \|	We need to test f-strings now and it's a bother making that compatible with Python 2.
*	Remove trailing whitespace	a1346054	2021-08-25	1	-1/+1
\|
*	Actions: Add on pull_request again	toonn	2021-07-24	3	-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 necessary	toonn	2021-07-20	3	-12/+0
\|
*	Actions: Reduce tested versions to oldest and newest	toonn	2021-07-20	3	-4/+4
\|
*	Actions: Fix Python and Pypy paths filters	toonn	2021-07-20	2	-3/+3
\|
*	Actions: Drop on_pullrequest from Pypy	toonn	2021-07-20	1	-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 filter	toonn	2021-07-20	2	-4/+4
\|
*	Actions: Drop Pypy from pylint and add pylint to Pypy	toonn	2021-07-20	2	-2/+2
\|
*	Actions: Update shellcheck required actions	toonn	2021-07-20	1	-3/+1
\|
*	Actions: Refine Pypy versions and title	toonn	2021-07-20	1	-2/+2
\|
*	Actions: Separate pypy tests because they fail	toonn	2021-07-20	3	-2/+36
\|
*	Actions: Update, incorporate and split	toonn	2021-07-20	3	-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 pylint	toonn	2021-07-20	1	-1/+1
\|
*	Actions: Set TERM=dumb to avoid tput warnings	toonn	2021-07-20	2	-0/+4
\|
*	Actions: Try to fix missing terminfo	toonn	2021-07-20	1	-0/+1
\|
*	Actions: Add on pull_request to get status checks	toonn	2021-07-20	3	-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 comment	toonn	2021-01-05	1	-1/+1
\|
*	Fix shellcheck download url	toonn	2021-01-05	1	-1/+1
\|
*	Document expected failure of GH Action	toonn	2020-07-05	1	-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 workflow	toonn	2020-07-05	2	-3/+3
\| \| \| \| \|	Add pytest to the failing workflow because otherwise it's not run with python 2.7.
*	Prepare for Pylint transition from versions <2	toonn	2020-07-05	3	-34/+4
\|
*	Seperate doctests and pytests	toonn	2019-09-24	2	-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 workflow	toonn	2019-09-18	1	-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.7	toonn	2019-09-18	1	-1/+1
\| \| \| \| \|	Temporarily drop python 3.7 from the workflow because it's not compatible with `pylint<2`.
*	Add GitHub Actions ci	toonn	2019-09-03	2	-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.