Comments (4)
Yes, I thought about something like that a while ago (see issue #11).
What do you mean by "activate by project"? Have all settings configured per project?
from limited-wip.
Pretty much (or maybe override by project). I have some projects no written by me that don't work well with TCR (where the tests can fail in surprising ways). Even the size of the commits can get out of hand because of changing data. In these projects, I'd like to either stop the plugin entirely or partly.
In my projects, I'm rather enjoying using it and it's really helping the flow of my work in general.
from limited-wip.
I had pretty much the same experience. The main reason I didn't implement it was that updating the same setting for each project can be very tedious. Maybe this is not really a problem and I should just try per-project settings.
from limited-wip.
I made all plugin settings to be scoped by current project.
Unfortunately, your current application-level settings will be lost on plugin update (because it's not very clear how to do migration, should the current settings become default for all new projects? probably not).
This should work starting from v0.3.6 once it's approved by jetbrains.
from limited-wip.
Related Issues (20)
- Commit without dialog action doesn't work in 2019.3 EAP HOT 2
- Feature Request: support timeout period less than 1 minute HOT 5
- not committing on test run HOT 5
- Commits on Compound test when one fails
- should not update shared misc.xml HOT 2
- Do you have plans to support this plugin in Rider? HOT 10
- TCR: support mode to commit/revert on expected red
- TCR: killing tests during long execution is considered a failure and reverts all changes
- Commits are still allowed even if you go over watchdog threshold
- Commit fails if reformat / optimise imports is enabled HOT 1
- TCR without revert
- Option to force entry of the commit message HOT 2
- Two commit dialogs open when tests run with Gradle run configuration
- AlreadyDisposedException: Cannot create com.intellij.openapi.vcs.ProjectLevelVcsManager
- Manual undo operation does not work properly after failing test
- feature idea: option to use test name for commit message in TCR mode HOT 1
- should the TCR mode automatically commit after I run a test? It doesn't seem to be committing. HOT 2
- Feature request: TCR option to prompt for commit message HOT 1
- Press "ok" before auto-reverting HOT 2
- Slow operations are prohibited on EDT
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from limited-wip.