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.

Sign up for GitHub

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

Jump to bottom

Clarify how to run Tailwind command in CI #230

Merged
merged 2 commits into from Dec 7, 2022
Merged

Clarify how to run Tailwind command in CI #230

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1246d9c
Clarify how to run Tailwind command in CI
ghiculescu Dec 5, 2022
9e8e60a
Update README.md
flavorjones Dec 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 6 additions & 1 deletion README.md
View file
Open in desktop
Expand Up @@ -28,8 +28,13 @@ The `tailwindcss:build` is automatically attached to `assets:precompile`, so bef

### Building for testing

The `tailwindcss:build` is automatically attached to `test:prepare`, which runs before Rails tests. (Note that this currently only applies to rails `test:*` tasks (like `test:all` or `test:controllers`), not "rails test", as that doesn't load `test:prepare`).
The `tailwindcss:build` task is automatically attached to the `test:prepare` Rake task. The `test:prepare` task is run before some test tasks (e.g. `test:all` and `test:controllers`), but not before the bare `test` task.

If your tests need Tailwind assets in your CI environment, it's best to be explicit and run this command:

```
bin/rails test:prepare test
```

### Update assets automatically

Expand Down