Problem: k8s docs not clear about who they're for#2439
Merged
muawiakh merged 1 commit intobigchaindb:masterfrom Aug 6, 2018
ttmc:add-note-atop-k8s-docs
Merged
Problem: k8s docs not clear about who they're for#2439muawiakh merged 1 commit intobigchaindb:masterfrom ttmc:add-note-atop-k8s-docs
muawiakh merged 1 commit intobigchaindb:masterfrom
ttmc:add-note-atop-k8s-docs
Conversation
Solution: Add a note atop k8s docs pages to clarify who they're for
muawiakh
approved these changes
Aug 6, 2018
Contributor
|
Will merge once travis is 🥗 |
Codecov Report
@@ Coverage Diff @@
## master #2439 +/- ##
======================================
Coverage 88% 88%
======================================
Files 40 40
Lines 2310 2310
======================================
Hits 2033 2033
Misses 277 277 |
Contributor
Author
|
@muawiakh Travis is now 🥗 |
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.
Solution: Add a note atop k8s docs pages to clarify who they're for
Notes: