dsmiley commented on PR #12131: URL: https://github.com/apache/lucene/pull/12131#issuecomment-2084240048
> if your file is in git, adding it to .gitignore doesn't make local changes ignorable - it's still versioned and git status would show it as modified. True; I had thought .gitignore kept this but it doesn't. In my projects where I have changed files that I never want to commit, I use an IntelliJ changelist I name "Ignored" that is never active. It prevents accidentally committing it. > org.gradle.workers.max=12 FYI: Runtime.runtime.availableProcessors() is 16 on my machine). I haven't found that particular setting to be so problematic for me since a build exclusive of tests (a) doesn't do *that* much (won't cripple my machine for 5+ minutes), and (b) is only partially parallelizable to a high level due to many dependencies. An advantage to a checked-in gradle.properties is keeping it up to date. A new setting might be added and it'll be used without concern over whether or not someone generated an old one -- that's a non-issue. I reviewed Gradle's [options](https://docs.gradle.org/current/userguide/build_environment.html) for configuration and did a little experiment. I'm happy to report that we can put individual settings in `~/.gradle/gradle.properties` and these settings will overlay in priority over those in the project's properties. Nice; ehh? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
