fix: select default init template by extension

[arnabnandy7]

Summary

Fixes #2635.

When jbang init is used without an explicit template, JBang now selects an available hello.<extension> template matching the requested file extension.

For example:

jbang init hello.kt

now uses the built-in hello.kt template instead of selecting the Java hello template and failing with:

Template expects java extension, not kt

The existing Java template remains the fallback for .java and extensionless filenames. Explicit template selection and extension validation remain unchanged.

Changes

• Select the default initialization template based on the requested extension.
• Add regression tests for Kotlin and Groovy initialization.
• Document extension-based default template selection.
• Document Kotlin script creation using jbang init hello.kt.

Verification

./gradlew test --tests "dev.jbang.cli.TestInit"

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• ai-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 52d36db6-a7de-41b3-89fa-a6a734739792

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a533550cbb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".