Attempt to deal with rose-stem project name for shared repository #1412
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
|
(@scwhitehouse I have not forgotten about this, but I am trying to see if we can find an alternate solution based on secondary location keywords.) |
|
I'll merge this in for now, but I think we need to find a better solution via FCM location keywords. |
matthewrmshin
added a commit
that referenced
this pull request
Oct 2, 2014
Attempt to deal with rose-stem project name for shared repository
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.
A simple way of dealing with . in fcm keywords for rose-stem as something which needs to be fixed before the shared repository. I'm not sure if this is the ideal solution, but it's probably the simplest. @matthewrmshin what do you think?