← Back to issue list

Move the init command to craft-application

View original Github issue

Metadata

Project
charmcraft
Number
#1153
Type
issue
State
closed
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

Closed without implementation. The migration of the init command to craft-application was abandoned or superseded, with no comments or merge details recorded.

Suggested action:

No scores available.

Issue body

### What needs to get done Flesh out and test https://github.com/canonical/charmcraft/tree/craft-app/init ### Why it needs to get done craft-application project

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without implementation. The migration of the init command to craft-application was abandoned or superseded, with no comments or merge details recorded.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 60
Confidence: 80
Support Request: 5
needs triage Task to move and flesh out the charmcraft init command into the craft-application library. Currently unlabelled, inactive for over a year, with no maintainer comments or assignee.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 40
Confidence: 85
Support Request: 10
close stale Task to move the init command to the craft-application project. Unlabelled, with zero comments and over three years of inactivity, indicating it has likely been abandoned or superseded.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 65
Confidence: 85
Support Request: 0
needs triage Migrate and test the charmcraft init command to craft-application. Open, unassigned, zero comments, inactive for 300+ days. Requires implementation and testing to complete.

Update history

Date Change
closed

Related issues

Issue Project State Summary Similarity
#360 Migrate non-lifecycle commands to craft-application rockcraft closed Closed without a documented resolution. Implementation discussion noted changing the InitCommand superclass from BaseCommand to AppCommand within craft-application. The migration remains unimplemented and effectively abandoned.
84%
#5098 Use upstream `init` command from craft-application snapcraft closed Closed without implementation. The upstream init command replacement remains abandoned, pending the unresolved craft-application dependency.
82%
#753 Migrate to craft-application's InitService rockcraft closed Closed without resolution or linked pull request. The migration to craft-application's InitService was abandoned or superseded.
82%
#4742 Migrate commands to craft-application command snapcraft closed Closed without implementation. The commands were not migrated to craft-application, and no resolution details were provided. The issue appears abandoned or superseded.
80%
#2316 Charmcraft init migrated to InitService charmcraft closed The bounty to migrate Charmcraft's init command to craft-application's InitService was closed without implementation. Multiple contributors submitted proposals, but maintainers declined to proceed, leaving the task abandoned.
76%
#359 Migrate remaining lifecycle commands to craft-application rockcraft closed Closed as abandoned. No pull requests or comments were created, indicating the migration of remaining lifecycle commands was not completed and superseded by later development.
76%
#1285 Migrate remaining commands to craft-application charmcraft closed Closed without implementation or linked pull requests. The tracking issue for migrating analyze, create-lib, fetch-lib, and list-lib commands to craft-application was abandoned or superseded by broader migration efforts.
75%
#1532 Use craft-application lifecycle commands charmcraft closed Closed without a documented fix or merge. Likely abandoned or superseded by upstream craft-application updates, as no resolution details were provided in the issue thread.
74%
#4468 feature/craft-application: migrate version command snapcraft closed Closed without comments or linked resolution. The version command migration to craft-application appears abandoned or superseded by subsequent refactoring. No merge or fix details were recorded.
74%