Impossible to create an issue non-interactively #162

nicoco commented 2025年01月09日 09:46:38 +01:00

I did not find how to create an issue non-interactively.

Attempt #1:

> berg --non-interactive issue create --title "test" --description "test description"
? Choose optional properties 
> [ ] Labels
 [ ] Assignees
 [ ] Milestone
[↑↓ to move, space to select one, → to all, ← to none, type to filter]

Attempt #2:

> berg --non-interactive issue create --title "test" --description "test description" --labels "" --assignees "" --milestone ""
┌─────────────────────────────────────────────────────────────────────────┐
│ There's nothing to select from │
│ │
│ Caused by: │
│ The prompt configuration is invalid: Available options can not be empty │
└─────────────────────────────────────────────────────────────────────────┘

For context, I am writing a script to migrate some projects from sourcehut, and using codeberg-cli looks like a good option.

I did not find how to create an issue non-interactively. Attempt #1: ```shell > berg --non-interactive issue create --title "test" --description "test description" ? Choose optional properties > [ ] Labels [ ] Assignees [ ] Milestone [↑↓ to move, space to select one, → to all, ← to none, type to filter] ``` Attempt #2: ```shell > berg --non-interactive issue create --title "test" --description "test description" --labels "" --assignees "" --milestone "" ┌─────────────────────────────────────────────────────────────────────────┐ │ There's nothing to select from │ │ │ │ Caused by: │ │ The prompt configuration is invalid: Available options can not be empty │ └─────────────────────────────────────────────────────────────────────────┘ ``` For context, I am writing a script to migrate some projects from [sourcehut](https://sr.ht), and using `codeberg-cli` looks like a good option.

Aviac commented 2025年01月10日 07:34:27 +01:00

Yeah it could be the case that most of the subcommands don't support non-interactive as of now since there wasn't really a use case for that yet. It should be easy to implement though. Could you please give me a list of commands you are going to need for your migration script here so I can make sure they all work?

Yeah it could be the case that most of the subcommands don't support `non-interactive` as of now since there wasn't really a use case for that yet. It should be easy to implement though. Could you please give me a list of commands you are going to need for your migration script here so I can make sure they all work?

nicoco commented 2025年01月10日 09:39:31 +01:00

Hey thanks for considering the request!

For my script I finally opted for python using clientapi_forgejo which is more feature complete, so I won't use berg for it anyway... But fixing the non-interactive usage would be great anyway. ;)

Hey thanks for considering the request! For my script I finally opted for python using [clientapi_forgejo](https://github.com/client-api/forgejo-python) which is more feature complete, so I won't use berg for it anyway... But fixing the non-interactive usage would be great anyway. ;)

Aviac commented 2025年09月15日 20:03:23 +02:00

This is fixed now as well as some other commands. Non-interactiveness support is growing :) I'm closing this here since the specific issue was resolved. Thanks for taking the time to create this issue 💚

This is fixed now as well as some other commands. Non-interactiveness support is growing :) I'm closing this here since the specific issue was resolved. Thanks for taking the time to create this issue 💚