Allow developers to have custom rspec output settings
What does this MR do?
Remove .rspec from the repository.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Rspec options in CI are controlled via various CI scripts. So there is no reason to have this file in version control for the sake of CI.
Outside of CI we are on individual contributor's development machines. There it would be nice to let the developer configure Rspec output using the $HOME/.rspec file. Because the project .rspec file overrides $HOME/.rspec that is currently a clumsy process.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Edited by Jacob Vosmaer