feat(just): verbose and quiet update messages

[bmp]

Verbose output with just disable-updates and prompts to update each command

[bobslept]

This PR gives some extra options when using just update on systems where ublue-update is disabled or not used. As shown below it defaults to full verbosity and also allows you to prompt per command.

~ ❯ just update help
Usage: just update <level>
  <level>: Specify the verbosity level - 'full', 'minimal', or 'prompt'
  Use 'full' to show full output of each command.
  Use 'minimal' to show minimal output and indicate success or failure.
  Use 'prompt' to prompt the user before running each command.

~ ❯ just update
Running rpm-ostree update...
note: automatic updates (stage) are enabled
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:39
No upgrade available.
Completed rpm-ostree update
Running flatpak update -y...
Looking for updates…

Nothing to do.
Completed flatpak update -y
Running distrobox upgrade -a...
Completed distrobox upgrade -a

~ ❯ just update minimal
Running rpm-ostree update...
Completed rpm-ostree update
Running flatpak update -y...
Completed flatpak update -y
Running distrobox upgrade -a...
Completed distrobox upgrade -a

~ ❯ just update prompt
Do you want to run rpm-ostree update? [Y/n]: n
Skipped rpm-ostree update
Do you want to run flatpak update -y? [Y/n]: n
Skipped flatpak update -y
Do you want to run distrobox upgrade -a? [Y/n]: y
Running distrobox upgrade -a...
Completed distrobox upgrade -a

~ ❯ 

Lets ask the @ublue-os/approver what they think of this.

[bsherman]

I did some testing with this and it looks nice.

Thank you for the submission!

[bmp]

@bsherman It continues to say merging is blocked, do I need to do anything else?

[bsherman]

@bsherman It continues to say merging is blocked, do I need to do anything else?

It can be merged after another member of the approval team gives approval.

[bmp]

It can be merged after another member of the approval team gives approval.

Understood, thank you!

[bsherman]

Oh, also @bmp ... can you modify your commit message to be semantic?

Instead of "Update 10-update.just" make it something like "feat(just): verbose and quiet update messages"

[bmp]

Oh, also @bmp ... can you modify your commit message to be semantic?

Instead of "Update 10-update.just" make it something like "feat(just): verbose and quiet update messages"

Done, made the change, is there a guide somewhere that I could read about appropriate commit messages?

[bsherman]

Done, made the change, is there a guide somewhere that I could read about appropriate commit messages?

Ah, you changed the title of the Pull Request. the automation for merge approval is called "Semantic PR" and it's enforcing a standard for our commit messages... https://www.conventionalcommits.org/en/v1.0.0/

The PR title is not the issue it's the commit message itself, which you can see here: https://github.com/ublue-os/config/pull/167/commits

Perhaps you can modify your commit message and force push to your repo and that will be reflected here?

[bmp]

@bsherman Thank you for the tips, I have made the changes and pushed the commit onto my repo. It seems like it passed Semantic PR check now :-). Now it needs another reviewer to approve I guess.

[bsherman]

Thank you for the tips,

You're welcome! Thanks for making the changes! I've asked some others to take a look.

[z0rrn]

Maybe a text behind the explanation of full like [default] would be good. I as a user sometimes want to know the default without looking into code.