Auto file sync before commit dialog
Hi folks
We have pretty straight forward project with git integration. But we need external tools for sass or js compilation - they are integrated with bash support for phpstorm, which means they run in the phpstorm terminal. Anyway: External changes are not regocnized by phpstorm (only on frame change, but that may never happen before a commit).
Our frontend developers, hance, are working in their .scss files for example and compass in our terminal automatically updates the according css files. But phpstorm never regonizes those changes. Only if we hit synchronize manually or if we switch tabs or windows on purpose.
All we basically need is, that phpstrom automatically synchronizes files before showing the git commit dialog. because our css files are not showing in the dialog, when we forgot to manually synchronize the local file system. It's just one of many examples, where file system changes are not regonized. but all our problems would be solved if the git commit dialog automatically refreshes the file system before showing itself. It there any possible way to achieve this? I've tried so many plugins, but to no avail.
Thanks and regards
请先登录再写评论。
Hi there,
Have you tried File Watcher instead of External Tools (or whatever you are using there)? It can refresh generated files after execution (if you specify them correctly, of course).
https://confluence.jetbrains.com/display/PhpStorm/File+Watchers+in+PhpStorm
Nothing on actual thread subject from me.
As mentioned, there are various changes to files from outsidethat can't be handled with sole filewatchers. Maybe i could get some of them to work (sass for example, but it's not as easy as we use compass to compile) to minimize the problem for some files. but a simple "auto refresh before git commit" would actually solve all problems, which is why I asked for exactly that.
If something as simple as that is not possible I may have to invest more time in trying to solve *all* cases with file watchers.
This is an old ticket but you may see what devs thought about such option back then:
https://youtrack.jetbrains.com/issue/IDEA-92278
>More important, forcing synchronize before commit doesn't seem to be a good idea as it will will delay appearance of commit things for indefinite time (especially on a large projects).
Could not find any better ticket with my search. Maybe JB team can help.
It's sad this was discussed five years ago. Maybe I should rethink and try using file watchers and/or change something in our process. Thanks for the link, didn't find that one - only many discussions about local/remote sync which isn't the actual problem here.