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

Lint Generator: Remove generated test/spec files #1167

Conversation

stevepolitodesign
Copy link
Contributor

@stevepolitodesign stevepolitodesign commented Mar 21, 2024

Follow-up to #1148

I noticed these tests did not fail even if bin/rails standard raised a
linting violation. Because the upcoming suspenders:ci generator will
run our linting tasks in CI, I felt having a test to do the same was no
longer warranted.

Follow-up to #1148

I noticed these tests did not fail even if `bin/rails standard` raised a
linting violation. Because the upcoming `suspenders:ci` generator will
run our linting tasks in CI, I felt having a test to do the same was no
longer warranted.
@stevepolitodesign stevepolitodesign force-pushed the suspenders-3-0-0-linting-generator-follow-up branch from 5799575 to 8aa6efb Compare March 21, 2024 13:12
@stevepolitodesign stevepolitodesign changed the title Lint Generator: Fix generated spec Lint Generator: Remove generated test/spec files Mar 21, 2024
@stevepolitodesign stevepolitodesign merged commit 39efb28 into suspenders-3-0-0 Mar 21, 2024
2 checks passed
@stevepolitodesign stevepolitodesign deleted the suspenders-3-0-0-linting-generator-follow-up branch March 21, 2024 13:15
stevepolitodesign added a commit that referenced this pull request May 10, 2024
Follow-up to #1148

I noticed these tests did not fail even if `bin/rails standard` raised a
linting violation. Because the upcoming `suspenders:ci` generator will
run our linting tasks in CI, I felt having a test to do the same was no
longer warranted.
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