| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
| |
Use info for changes performed (e.g. changes to the filesystem, code
executed). Use verbose for "nothing to do" messages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This forces Dotbot to produce colored output, regardless of whether it
is outputting to a TTY.
This is useful to support use cases such as piping colored Dotbot output
into another program for formatting (e.g. I want to indent the output as
part of a larger installation script); this was not previously easy to
do as this would cause the output to lose its colored formatting.
This option cannot be provided at the same time as the existing
`--no-color` option, as there's no logical interpretation of what effect
providing both of these should have.
As part of this change I've refactored some existing code determining
whether output should be colored to where options are parsed, as this
made this change simpler and I think it makes sense for all this logic
to be performed in the same place.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the setup guide in the README, we have people start out with an empty
file (created using `touch`). Before this patch, Dotbot gave the
following error:
Configuration file must be a list of tasks
Instead, with this patch, Dotbot says:
Configuration file is empty, no work to do
This change was prompted by
https://github.com/anishathalye/dotbot/pull/226.
|
| |
|
|
|
|
| |
Internal to Dotbot, we use the name "skip" instead of "except", because
the latter is a keyword, and using a name like "except_" didn't seem as
nice.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
By default, if output is a TTY, dotbot will colorize the output. This
patch adds the option to pass `--no-color` to dotbot to have it suppress
this colorization.
|
| | |
|
| |
|
|
|
| |
This patch also makes the '-d' argument optional, with the base
directory defaulting to the directory of the configuration file.
|
| |
|
|
|
|
|
|
| |
Prior to this patch, Dotbot was relying on running with the base
directory being the current working directory. In practice, it was
relying on the install shim to set up this context. It makes more sense
sense to actually execute `chdir()` within Dotbot itself, rather than
relying on the install shim to do so.
|
| | |
|
| |
|
|
|
| |
This patch makes Dotbot warn the user and gracefully exit when the
configuration file is not a list.
|
| |
|
|
| |
Fix formatting of keyword arguments according to PEP 8.
|
| | |
|
| |
|
