Eventually the database will increase in size, so the --list will almost become useless (too long).
Maybe adding an option to remove old states will help the user be more in control.
We can have the same formula we have for mirro. See here.
an environment variable CHGUARD_STATES_LIFE that will manage the life (in days) of the states
this can be added into the user's .bashrc
a default value for that variable (e.g. 30)
ability to override that value with chguard --prune-states=14
Eventually the database will increase in size, so the `--list` will almost become useless (too long).
Maybe adding an option to remove old states will help the user be more in control.
We can have the same formula we have for `mirro`. [See here](https://git.sysmd.uk/guardutils/mirro#remove-old-backup-files).
- an environment variable `CHGUARD_STATES_LIFE` that will manage the life (in days) of the states
- this can be added into the user's `.bashrc`
- a default value for that variable (e.g. 30)
- ability to override that value with `chguard --prune-states=14`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Eventually the database will increase in size, so the
--listwill almost become useless (too long).Maybe adding an option to remove old states will help the user be more in control.
We can have the same formula we have for
mirro. See here.CHGUARD_STATES_LIFEthat will manage the life (in days) of the states.bashrcchguard --prune-states=14