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

Add list of factors to main description for decision-making area #62

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

rainmaker
Copy link
Contributor

There's an item on the first page that asks about basic consideration of these factors, and people need to go to the next page for a complete list of them. Seemed like an easy thing to streamline so people can fully answer the first page questions.

@rainmaker rainmaker changed the title Add list of factors to main description for decision-making are Add list of factors to main description for decision-making area Oct 25, 2019
rosenhouse
rosenhouse previously approved these changes Oct 26, 2019
@rainmaker rainmaker self-assigned this Nov 5, 2019
@rosenhouse
Copy link
Member

I'm concerned now that the bullets won't show up nicely on the form itself, since the text description there becomes plaintext, and only respects double line-breaks

@rosenhouse rosenhouse dismissed their stale review November 5, 2019 20:34

formatting, eh

@rainmaker rainmaker force-pushed the technical-decision-factors branch from ee78fae to e8520bd Compare November 8, 2019 18:47
There's an item on the first page that asks about basic
consideration of these factors, and people need to go to the next page
for a complete list of them.
@rainmaker rainmaker force-pushed the technical-decision-factors branch from e8520bd to 4a7eaae Compare November 8, 2019 18:48
..after checking the format on the google form
@rainmaker
Copy link
Contributor Author

rainmaker commented Nov 13, 2019

I checked, and I feel pretty confident that this will show up nicely on the form. We may not immediately be able to update everyone's forms with the new description, but it will eventually be possible when we address #48

@rainmaker
Copy link
Contributor Author

@rosenhouse Should we hold this PR until it'll update on the form? Having concerns about pushing a change that will cause a noticeable desync between the markdown and forms.

@rosenhouse
Copy link
Member

rosenhouse commented Nov 13, 2019

I understand that concern. I'm ok to merge it anyway. I don't feel strong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants