Skip to content

Reorganize rust crates into a flat crates directory, simplify some CI steps#4496

Merged
maxbrunsfeld merged 8 commits intomasterfrom
reorganize-dirs
Jun 6, 2025
Merged

Reorganize rust crates into a flat crates directory, simplify some CI steps#4496
maxbrunsfeld merged 8 commits intomasterfrom
reorganize-dirs

Conversation

@maxbrunsfeld
Copy link
Contributor

@maxbrunsfeld maxbrunsfeld commented Jun 6, 2025

This makes the project less confusing to navigate by reorganizing the file structure. The core library is still in the top-level lib folder, because it also contains the C source code, but all of the CLI-related crates are now flattened under a top-level crates folder, like many other multi-crate Rust repos.

Also, I've removed some CI steps that are adding friction to my own contributions. We no longer install rust nightly in addition to Rust stable for clippy and fmt. I don't want formatting failures in CI that will not match what I do normally during local development. Cargo fmt happens when I save files, but only on one Rust toolchain, not multiple. Wherever possible, I want our formatting checks to just enforce the normal rust defaults, nothing custom or extra-pedantic.

@maxbrunsfeld maxbrunsfeld changed the title Reorganize rust crates into a flat crates directory Reorganize rust crates into a flat crates directory, simplify some CI steps Jun 6, 2025
@maxbrunsfeld maxbrunsfeld enabled auto-merge (squash) June 6, 2025 21:25
@maxbrunsfeld maxbrunsfeld disabled auto-merge June 6, 2025 21:25
@maxbrunsfeld maxbrunsfeld merged commit 0fdf569 into master Jun 6, 2025
19 checks passed
@maxbrunsfeld maxbrunsfeld deleted the reorganize-dirs branch June 6, 2025 21:25
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.

Also throttle the build step to 10 parallel tasks (reduces flakiness on
Windows).
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.

Also throttle the build step to 10 parallel tasks (reduces flakiness on
Windows) and raise the limit for the generate step to 3 (reduces the
chance of timeouts).
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.

Also throttle the build step to 10 parallel tasks (reduces flakiness on
Windows) and raise the limit for the generate step to 3 (reduces the
chance of timeouts).
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.

Also throttle the build step to 10 parallel tasks (reduces flakiness on
Windows) and raise the limit for the generate step to 3 (reduces the
chance of timeouts).

Also raise the timeout limit to 30 minutes (it's more expensive to have
to restart flaky tests than to let them run).
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.

Also throttle the build step to 10 parallel tasks (reduces flakiness on
Windows).

Also raise the timeout limit to 30 minutes (it's more expensive to have
to restart flaky tests than to let them run).
clason added a commit that referenced this pull request Jun 27, 2025
Problem: After #4496, the
crater tests from nvim-treesitter no longer run on PRs with relevant changes.

Solution: Update the paths in the workflows to the new structure.

Also throttle the build step to 10 parallel tasks (reduces flakiness on
Windows).

Also raise the timeout limit to 30 minutes (it's more expensive to have
to restart flaky tests than to let them run).
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.

1 participant