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

Ignore paths in .gitignore for Stylelint #589

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

karlhorky
Copy link
Member

If Playwright has generated a report, this causes Stylelint failures (see below). Instead we should ignore files using .gitignore for Stylelint.

$ preflight
πŸš€ UpLeveled Preflight v8.0.1
√ All changes committed to Git
√ node_modules/ folder ignored in Git
√ No extraneous files committed to Git
√ No secrets committed to Git
√ Use single package manager
√ Project folder name matches correct format
√ No dependency problems
√ GitHub repo has deployed project link under About
√ ESLint
Γ— Stylelint
  β€Ί Stylelint problems found in the following files:
  playwright\report\trace\codeMirrorModule.ez37Vkbh.css
  playwright\report\trace\inspectorTab.DLjBDrQR.css
  playwright\report\trace\uiMode.CAYqod-m.css
  playwright\report\trace\workbench.D3JVcA9K.css

  Open these files in your editor - there should be problems to fix
√ Prettier
√ ESLint config is latest version
√ Stylelint config is latest version
√ Preflight is latest version

Copy link

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@karlhorky karlhorky changed the title Ignore paths in .gitignore for Stylelint Ignore paths in .gitignore for Stylelint Oct 17, 2024
@karlhorky karlhorky merged commit a96ed9d into main Oct 17, 2024
7 checks passed
@karlhorky karlhorky deleted the ignore-paths-in-gitignore-in-stylelint branch October 17, 2024 09:13
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.

2 participants