Restore replying functionality inside Flowdock while keeping avatars.#9
Open
blackxored wants to merge 2 commits into
Open
Restore replying functionality inside Flowdock while keeping avatars.#9blackxored wants to merge 2 commits into
blackxored wants to merge 2 commits into
Conversation
added 2 commits
September 8, 2013 17:04
Now (at least in theory) you can still respond directly inside Flowdock to have the content reflected back in the Sprint.ly systems. At that commit I wasn't aware than the email changes would break this but after reading that it was a blocking point in #1, I decided to fix it properly.
Author
|
What's the status of this? |
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
1 participant
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.
Now (at least in theory) you can still respond directly inside Flowdock to have the content reflected back in the Sprint.ly systems.
At fc1dca7 I wasn't aware than the email changes would break this but after reading that it was a blocking point in #1, I decided to fix it properly.
Comments on Flowdock should now get routed back to Sprint.ly.
Please confirm this is the case and close this.