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

Grunt deploy tasks create "Unversioned Files" in chipper/eslint/cache/ #390

Closed
pixelzoom opened this issue Oct 28, 2024 · 2 comments
Closed

Grunt deploy tasks create "Unversioned Files" in chipper/eslint/cache/ #390

pixelzoom opened this issue Oct 28, 2024 · 2 comments
Assignees
@pixelzoom
Labels
status:ready-for-review type:bug

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Oct 28, 2024 •
edited
Loading

After running one of the grunt deploy tasks (rc, production,...) on a release branch, chipper/eslint/cache/ gets populated, and WebStorm reports them as "Unversioned Files" -- see screenshot below, after grunt production for unit-rates. Then they must be manually deleted.

Should grunt deploy tasks automatically delete these files? Or should they be added to ignored directories in WebStorm? Or something else?

screenshot_3553
@zepumph
Copy link
Member

zepumph commented Oct 28, 2024

Duplicate of phetsims/chipper#1508. Please pull and review if this is acceptable.

@zepumph zepumph assigned pixelzoom and unassigned zepumph Oct 28, 2024
@pixelzoom
Copy link
Contributor Author

What you described in phetsims/chipper#1508 sounds reasonable. I don't have time to test-drive, so I'll assume that you did. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pixelzoom pixelzoom

Labels
status:ready-for-review type:bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pixelzoom @zepumph