As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

• Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
• Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Should be straight forward now with this: https://github.com/eriwen/gradle-completion

I am guessing that it is too late in the game anyway to make such a change, but the issue is not solved by gradle-completion. Gradle-completion only helps for running gradle. An example is editing the build file, I type "vi b<tab>" and instead of completing to "build.gradle" bash can only complete to "build" because of the directory.

Just my $0.02.

Yeah, there's no way we will change the conventions from build.gradle to a different name. Also, the buildDir default is set in stone. In case you prefer different names then you can still configure your build to use different ones.