Fixing error when launching Alex without private configs. - #122
Open
ticcky wants to merge 1 commit into
Open
Conversation
Member
|
@ticcky what will happen if you want to add the private git repository? |
Contributor
Author
|
That's right Ondra. Thanks! I think the best thing would be actually to remove the include from the config file altogether, and actually have the include in the secret file but in reverse. What do you think? |
Member
|
Well, is it really necessary to include one into another or vise versa? |
Contributor
Author
|
That is even better. I will discuss it with Filip. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adding an empty file that will prevent Alex from failing because of including private files from the main config that do not exist in case somebody is using Alex without the private repository.