Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistently use question mark suffix for question node keys in docs #2392

Merged
merged 1 commit into from
Mar 22, 2016

Conversation

floehopper
Copy link
Contributor

Documentation change only.

@floehopper floehopper added the documentation Improvements or additions to documentation label Mar 21, 2016
@@ -73,5 +73,5 @@ Occurs if the `next_node` blocks returns a value that isn't defined as a questio
next_node do
outcome :red
end
outcome :green
outcome :green?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this one should've been changed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I've changed it to outcome :blue so that it's less confusing. Fix-up commit: 87af37e.

@chrisroos
Copy link
Contributor

Aside from one change that doesn't look right, this all looks good to me.

@chrisroos chrisroos self-assigned this Mar 22, 2016
@chrisroos chrisroos added the LGTM label Mar 22, 2016
@floehopper
Copy link
Contributor Author

Rebasing to incorporate fix-up commit, then rebasing against master, resolving conflicts and force-pushing in preparation for merge.

@floehopper floehopper force-pushed the fix-question-node-keys-in-docs branch from 87af37e to e9f93ec Compare March 22, 2016 10:51
floehopper added a commit that referenced this pull request Mar 22, 2016
Consistently use question mark suffix for question node keys in docs
@floehopper floehopper merged commit b610ece into master Mar 22, 2016
@floehopper floehopper deleted the fix-question-node-keys-in-docs branch March 22, 2016 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants