-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - ci(scripts/*): linting for copyright, imports, module docstrings, line length #4486
[Merged by Bors] - ci(scripts/*): linting for copyright, imports, module docstrings, line length #4486
Changes from all commits
0296cb5
8b2a6a6
d6b96b8
0d90a8c
54c69c7
f1d572b
0947fef
8664a96
466623c
99bdeb8
d41c321
5caa01f
f080aaa
d1df3b9
c510fbc
319c624
6d3d425
ffb10a8
6560f6a
9eed9ec
9b251b6
0e3f228
5484cca
f9492d1
8377549
fcb6e59
72bbc94
12d651c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,8 +30,8 @@ jobs: | |
set -o pipefail | ||
curl https://raw.githubusercontent.com/Kha/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain none -y | ||
~/.elan/bin/lean --version | ||
echo "::add-path::$HOME/.elan/bin" | ||
echo "::set-env name=short_lean_version::$(~/.elan/bin/lean --run scripts/lean_version.lean)" | ||
echo "$HOME/.elan/bin" >> $GITHUB_PATH | ||
echo "short_lean_version=$(~/.elan/bin/lean --run scripts/lean_version.lean)" >> $GITHUB_ENV | ||
|
||
- name: install azcopy | ||
run: | | ||
|
@@ -94,7 +94,7 @@ jobs: | |
set -o pipefail | ||
curl https://raw.githubusercontent.com/Kha/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain none -y | ||
~/.elan/bin/lean --version | ||
echo "::add-path::$HOME/.elan/bin" | ||
echo "$HOME/.elan/bin" >> $GITHUB_PATH | ||
|
||
- name: lint | ||
run: | | ||
|
@@ -119,7 +119,7 @@ jobs: | |
set -o pipefail | ||
curl https://raw.githubusercontent.com/Kha/elan/master/elan-init.sh -sSf | sh -s -- --default-toolchain none -y | ||
~/.elan/bin/lean --version | ||
echo "::add-path::$HOME/.elan/bin" | ||
echo "$HOME/.elan/bin" >> $GITHUB_PATH | ||
|
||
- name: install Python | ||
uses: actions/setup-python@v1 | ||
|
@@ -144,3 +144,7 @@ jobs: | |
python scripts/yaml_check.py docs/100.yaml docs/overview.yaml docs/undergrad.yaml | ||
bash scripts/mk_all.sh | ||
lean --run scripts/yaml_check.lean | ||
|
||
- name: check for copyright headers and module docstrings | ||
run: | | ||
Comment on lines
+147
to
+149
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can this be run before any of the really slow build steps? I don't want to wait hours for a build, only for it to then say my line is too long and have to start all over again because the file I wrapped the line in needs rebuilding. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My reasoning was the opposite; since fixing the issues caught by this script shouldn't typically create new build / linter issues, it's better to report those "more serious" problems first so that those can be addressed / discussed. For example, fixing a build / linter issue (e.g. from a github suggestion) might temporarily make a line too long, and I think it'd be better to first check that the suggestion "works" rather than force people to reflow everything up front. Feel free to bring this up on Zulip, I'd be curious to hear others' thoughts on this as well. Note that you should be able to run this script manually by executing |
||
./scripts/lint-copy-mod-doc.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not unhappy with the change, but it's completely unrelated, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, Bryan mentioned a link to a GH blog post about some vulnerability that is fixed by this change.