Skip to content

Commit e5d8938

Browse files
committed
lint-history: explain how TMPDIR can be used
Some users may want to take advantage of setting TMPDIR to another location that might be faster for the linting process. Reported-by: @ruv on GitHub Signed-off-by: Elijah Newren <[email protected]>
1 parent ccc37d3 commit e5d8938

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

contrib/filter-repo-demos/lint-history

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,14 @@ EXAMPLES
7272
7373
To run eslint --fix on all .js files in history:
7474
lint-history --relevant 'return filename.endswith(b".js")' eslint --fix
75+
76+
INTERNALS
77+
78+
Linting of files in history will be done by writing the files to a
79+
temporary directory before running the linting program; the
80+
location of this temporary directory can be controlled via the
81+
TMPDIR environment variable as per
82+
https://docs.python.org/3/library/tempfile.html#tempfile.mkdtemp.
7583
'''
7684

7785
parser = argparse.ArgumentParser(description='Run a program (e.g. code formatter or linter) on files in history',

0 commit comments

Comments
 (0)