-
Notifications
You must be signed in to change notification settings - Fork 341
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] - chore(scripts): require all scripts to be documented in the README #14539
Conversation
@semorrison You may be interested in this one: obviously, it's not ready to land yet. |
PR summary fbd5774b08Import changes for modified filesNo significant changes to the import graph Import changes for all files
Declarations diff
You can run this locally as follows## summary with just the declaration names:
./scripts/declarations_diff.sh <optional_commit>
## more verbose report:
./scripts/declarations_diff.sh long <optional_commit> The doc-module for |
f332ff6
to
ee8a6aa
Compare
In detail, this PR - moves the executable bit check into the .yml files, instead of the shell script - adds a `--fix` flag to `lint-style`, for fixing style errors (when possible) - moves calling `lint-style.py` into `lake exe lint-style`, and - switches the CI workflow to call `lake exe lint-style` instead, and removes `lint-style.sh` Ideally, `lint-style.py` will be completely rewritten in Lean soon, so this calling of an external process is only temporary. Helps with #14539.
In detail, this PR - moves the executable bit check into the .yml files, instead of the shell script - adds a `--fix` flag to `lint-style`, for fixing style errors (when possible) - moves calling `lint-style.py` into `lake exe lint-style`, and - switches the CI workflow to call `lake exe lint-style` instead, and removes `lint-style.sh` Ideally, `lint-style.py` will be completely rewritten in Lean soon, so this calling of an external process is only temporary. Helps with #14539.
In detail, this PR - moves the executable bit check into the .yml files, instead of the shell script - adds a `--fix` flag to `lint-style`, for fixing style errors (when possible) - moves calling `lint-style.py` into `lake exe lint-style`, and - switches the CI workflow to call `lake exe lint-style` instead, and removes `lint-style.sh` Ideally, `lint-style.py` will be completely rewritten in Lean soon, so this calling of an external process is only temporary. Helps with #14539.
In detail, this PR - moves the executable bit check into the .yml files, instead of the shell script - adds a `--fix` flag to `lint-style`, for fixing style errors (when possible) - moves calling `lint-style.py` into `lake exe lint-style`, and - switches the CI workflow to call `lake exe lint-style` instead, and removes `lint-style.sh` Ideally, `lint-style.py` will be completely rewritten in Lean soon, so this calling of an external process is only temporary. Helps with #14539.
Apologies this rotted. I just merged I like this! Please merge if you are too, otherwise we can discuss what remains to be done. bors d+ |
✌️ grunweg can now approve this pull request. To approve and merge a pull request, simply reply with |
… them can come later.
Thank you for documenting most entries! I just took a pass over the ones I know, and formatted the file consistently. This is just missing an entry on ~four scripts used to generate the PR summary comment. Help on these is still welcome - though in my opinion, this is already useful. From my point of view, this can be merged. @bryangingechen I saw you self-assigned this. If I don't hear objections from you, I will merge this in a day (or so). |
I pushed a possible categorization of the remaining scripts with some details. Let me know if this is good! A lot of these files also have individual docs, so the combination of the generic dispatch and the specific information is probably good enough. |
Thanks for adding the last missing docs! I like the changes and just pushed a last tweak. I consider this really really ready now. |
Nice! Thank @grunweg for making this happen, and @adomani and @jcommelin for contributing documentation. I feel much better about our scripts/ directory now! Next up, rewrite all the python ones in lean. :-) bors merge |
…14539) This is valuable so - contributors can discover existing useful tools, - existing knowledge is documented and not lost - it (hopefully) inspires to re-consider if all each script is useful/why we have it. Having a [bounded number of entry-points](https://matklad.github.io/2023/12/31/O(1)-build-file.html) to CI is useful to have. This is implemented as a new check, piggy-backing the `lint_style` executable. To make CI pass, this PR adds a README file to `scripts`, containing stub descriptions for the current files. Future PRs should fill this out. Co-authored-by: Kim Morrison <[email protected]> Co-authored-by: Michael Rothgang <[email protected]> Co-authored-by: Damiano Testa <[email protected]>
Build failed: |
Haha, it caught a new one that has arrived on |
bors merge |
…14539) This is valuable so - contributors can discover existing useful tools, - existing knowledge is documented and not lost - it (hopefully) inspires to re-consider if all each script is useful/why we have it. Having a [bounded number of entry-points](https://matklad.github.io/2023/12/31/O(1)-build-file.html) to CI is useful to have. This is implemented as a new check, piggy-backing the `lint_style` executable. To make CI pass, this PR adds a README file to `scripts`, containing stub descriptions for the current files. Future PRs should fill this out. Co-authored-by: Kim Morrison <[email protected]> Co-authored-by: Michael Rothgang <[email protected]> Co-authored-by: Damiano Testa <[email protected]>
Build failed: |
bors merge |
…14539) This is valuable so - contributors can discover existing useful tools, - existing knowledge is documented and not lost - it (hopefully) inspires to re-consider if all each script is useful/why we have it. Having a [bounded number of entry-points](https://matklad.github.io/2023/12/31/O(1)-build-file.html) to CI is useful to have. This is implemented as a new check, piggy-backing the `lint_style` executable. To make CI pass, this PR adds a README file to `scripts`, containing stub descriptions for the current files. Future PRs should fill this out. Co-authored-by: Kim Morrison <[email protected]> Co-authored-by: Michael Rothgang <[email protected]> Co-authored-by: Damiano Testa <[email protected]>
Pull request successfully merged into master. Build succeeded: |
@kim-em I do have some in-progress PRs regarding this; review welcome :-)
|
…14539) This is valuable so - contributors can discover existing useful tools, - existing knowledge is documented and not lost - it (hopefully) inspires to re-consider if all each script is useful/why we have it. Having a [bounded number of entry-points](https://matklad.github.io/2023/12/31/O(1)-build-file.html) to CI is useful to have. This is implemented as a new check, piggy-backing the `lint_style` executable. To make CI pass, this PR adds a README file to `scripts`, containing stub descriptions for the current files. Future PRs should fill this out. Co-authored-by: Kim Morrison <[email protected]> Co-authored-by: Michael Rothgang <[email protected]> Co-authored-by: Damiano Testa <[email protected]>
This is valuable so
This is implemented as a new check, piggy-backing the
lint_style
executable.To make CI pass, this PR adds a README file to
scripts
, containing stub descriptions for the current files. Future PRs should fill this out.