Skip to content
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

Remove bin/fastcheck from bin/check script #361

Merged
merged 1 commit into from Mar 22, 2024

Conversation

lukasbischof
Copy link
Member

Executing bin/fastcheck in bin/check causes it to be executed twice on the CI and thus increasing CI time. In some projects, this was already removed. We should do the same for all other projects as well to keep it consistent and fast

@@ -58,7 +58,7 @@ They are always idempotent (runnable multiple times).
* Add a `bin/check` file. It will run all the automated tests. It's mainly used in our CI.

```sh
echo "#\!/usr/bin/env bash\nset -euo pipefail\nbin/fastcheck\nbin/rails zeitwerk:check" > bin/check
echo "#\!/usr/bin/env bash\nset -euo pipefail\n\nbin/rails zeitwerk:check" > bin/check
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a double new line increases readability and we also have it this way in other projects as well (e.g. mtextur, remms)

@lukasbischof lukasbischof force-pushed the feature/update-bin-check-template branch from a6ba35f to 90f6159 Compare March 22, 2024 10:19
@lukasbischof lukasbischof requested review from coorasse and a team March 22, 2024 10:19
Copy link
Member

@rnestler rnestler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally agree. In a related note: I'd rename it from "fastcheck" to "lint", since in practice we only run linters in it.

@lukasbischof
Copy link
Member Author

lukasbischof commented Mar 22, 2024

I'd rename it from "fastcheck" to "lint", since in practice we only run linters in it.

I also like this naming better than fastcheck (in my opinion, fastcheck is a bad name as it's not apparent what it does, especially in presence of a check script. The name suggest that it just runs the tests faster but actually it does not run any tests at all). However, this would either produce different namings in newer projects or a lot of pull requests moving a file

@coorasse
Copy link
Member

Agree! I am also in favor of renaming, but let's move on with this change in the meantime.

@coorasse coorasse merged commit 47e45b1 into main Mar 22, 2024
1 check passed
@coorasse coorasse deleted the feature/update-bin-check-template branch March 22, 2024 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants