Proposed feature: global configuration file

[jonasbn]

🔤 User Story

As a developer
I can specify a a global configuration file
so I do not have to specify my favorite command line options on every invocation of stevedore across repositories/projects

ℹ️ Notes

• Since stevedore has several command line flags, it would be nice to support a configuration file, so preferred behavior could be based on a central configuration
• The configuration file could control:
  • exclusion
  • inclusion
  • colors
  • color output
  • color inversion
  • verbosity
  • debug level
  • path to global ignore file
  • full path output
  • no full path output
• The configuration file could be located in:
  • $HOME/.config/stevedore.json
  • or in a local repository as .stevedore.json
  • The local file could have precedence over the global one
• This story originates from issue Proposed feature: configuration file #11
  • implementation introduced with version v0.9.0

🆗 Acceptance Criteria

• I can specify a global configuration file in $HOME/.config/
• I can specify a global configuration file as $HOME/.config/stevedore.json
• The local configuration file take precedence over the global one
• Command line options take precedence over configuration files

➡️ Resources and References

• XDG Base Directory Specification