feat: configure title and contentImage #1
Merged
Conversation
This file contains 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
|
@petrbela where do you see that token? I was under the impression that it's encrypted?! |
|
Oh yes you're right. Sorry about the confusion. |
|
no worries, I'll test and most likely merge this tomorrow. thanks for the contribution! |
Turbo87
added a commit
that referenced
this pull request
Feb 27, 2015
feat: configure title and contentImage
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.
Added some configuration options.
Btw you have your private npm token in
.travis.yml, you should put that in the env vars in travis (and change it now that it's been exposed).