[LoweRAM]

Summary

The --force option in charmcraft init had help text indicating it was needed to Initialize even if the directory is not empty (will not overwrite files). In reality, charmcraft init already allows non-empty directories as long as existing files do not conflict with the template. The --force flag is only required when files collide, in which case it permits initialisation without overwriting the conflicting files.

This change updates:

• The --force option help text and command overview in charmcraft/application/commands/init.py.

Verification

• make format
• make lint-code
• make test-fast

[lengau]

Removing myself since it was my robot who made this.

CC @tromai and @dwilding since this affects what we discussed in #2921

[Copilot]

🟢 Approval recommended

The documentation accurately reflects the existing initialization behavior, with no unresolved review issues.

No open issues 🎉

What changed in this PR

Clarifies the behavior of charmcraft init --force, explaining that non-empty directories are supported and that --force is only required when template files conflict with existing files.

Changes:

• Updates the init command overview with collision behavior.
• Clarifies that existing files are not overwritten.
• Revises the --force option help text.

File	Description
charmcraft/​application/​commands/​init.py	Updates the init command overview and --force option help text.

_{Review effort: Lite}

[jahn-junior]

Thanks!