We support two flows when registering:

Upfront (arguments):

atuin register -u "..." -e "..." -p "..."

Partial (prompt):

atuin register -u "..." -e "..."
Please enter password: ...

I think we should probably suggest the latter (it's uncommon to paste passwords into the command itself)

There's also the issue that the password prompt does not enable any proper p

What problem does this feature solve?

Example use case:
A static generated app with thousands of routes, like an e-commerce having a route for each product.
Apart from scheduling nuxt generate to run periodically and generate all static and dynamic routes, it would be nice to have the possibility to generate the static files for a single route, for example in a hook when the related ba

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

Proposal

As disscuseed on kedacore/keda#2765 (comment), we should unify the functions for Status & Conditions handling. Referencing controller related stuff here is suboptimal.

There are two locations with similar functions:
https://github.com/kedacore/keda/blob/9f0ee58fc6839d74636e1ec6883fe21d82617ea3/controllers/keda/util/status.go#L30-L63
https://g