You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So we can have a standard .cfg file and people (including myself) can edit their config files with their information without fear of commiting their API key (like I almost did right now).
Move combine.cfg to combine-example.cfg
Add combine.cfg to .gitignore
All instances of ConfigParser should note the existence of combine-example.cfg if combine.cfg is not found and output an appropriately helpful error message, then exit.
The text was updated successfully, but these errors were encountered:
So the first and second points are common (and trivial). But I would do it as:
Move combine.cfg to combine-example.cfg
Add combine.cfg to .gitignore
All instances of ConfigParser should note the existence of combine-example.cfg if combine.cfg is not found and output an appropriately helpful error message, then exit.
So we can have a standard .cfg file and people (including myself) can edit their config files with their information without fear of commiting their API key (like I almost did right now).
combine.cfg
tocombine-example.cfg
combine.cfg
to.gitignore
combine-example.cfg
ifcombine.cfg
is not found and output an appropriately helpful error message, then exit.The text was updated successfully, but these errors were encountered: