Draft Create Auto Detect .gradle file during Java detection

Open
#224 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, java
Domain
build-system

Research direction

Start by tracing the Java detection flow invoked by draft create, using the reported codecov/example-java-gradle repository as the reproduction case. Check how the tool distinguishes Gradle from Maven and add coverage for repositories containing *.gradle files. Done means Gradle projects are detected without prompting for a build system.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
When running draft create on the following repo, draft prompts for gradle or maven https://github.com/codecov/example-java-gradle

[Draft] --- Detecting Language ---
Use the arrow keys to navigate: ↓ ↑ → ←
? Linguist detected Java, are you using maven or gradle?:
  > gradle
    maven

Mention what platform you want to support the new feature
OSS

Describe the solution you'd like
Draft should detect the *.gradle files in a repository to determine if gradle is used.

Describe alternatives you've considered
A better method for detecting gradle or maven could be used. The build files are the best way I could determine.

Additional context
(none)

Dominant language
Go
Stars
644
Forks
74
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/draft

All issues in Azure/draft

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.