Stop committing JSON configuration to repo #20
Labels
No labels
bug
config update
documentation
duplicate
enhancement
in dev
input needed
new feature
not in draft
refactor
waiting on docs update
wont-do
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Sirdog/EnduraBot#20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rightfully pointed out by SierraKomodo is that the benefits of using json for configurable values is defeated if the json is committed to the repository with real values. At that point it doesn't make sense to parse the json: I should just use global variables.
I would like to keep things configurable, so I need to decouple the configuration files from the repo.
Additionally, I should try to condense some of the json files into one, instead of having so many.