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

event form test #1231

Merged
merged 2 commits into from Feb 2, 2017
Merged

event form test #1231

merged 2 commits into from Feb 2, 2017

Conversation

jywarren
Copy link
Member

@jywarren jywarren commented Feb 2, 2017

Make sure these boxes are checked before your pull request is ready to be reviewed and merged. Thanks!

  • all tests pass -- rake test:all
  • code is in uniquely-named feature branch, and has been rebased on top of latest master (especially if you've been asked to make additional changes)
  • pull request is descriptively named with #number reference back to original issue
  • if possible, multiple commits squashed if they're smaller changes

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/wiki/contributing-to-public-lab-software

We have a loose schedule of reviewing and pulling in changes every Tuesday and Friday, and publishing changes on Fridays. Please alert developers on plots-dev@googlegroups.com when your request is ready or if you need assistance.

Thanks!

@PublicLabBot
Copy link

PublicLabBot commented Feb 2, 2017

2 Warnings
⚠️ This pull request doesn’t link to a issue number. Please refer to the issue it fixes (if any) in the format: Fixes #123.
⚠️ You have added multiple commits. It’s helpful to squash them if the individual changes are small.
1 Message
📖 @jywarren Thank you for your pull request! I’m here to help with some tips and recommendations. Please take a look at the list above and help us review and accept your contribution!

Generated by 🚫 danger

@jywarren
Copy link
Member Author

jywarren commented Feb 2, 2017

Hi, @ananyo2012 -- do you think we could show something like "Tips" or "Suggestions" instead of "Warnings" to be a bit more encouraging?

@jywarren
Copy link
Member Author

jywarren commented Feb 2, 2017

Also, this now makes the issue fail if not every one is completed. I didn't realize that was the case. I think we should make them optional!

@ananyo2012
Copy link
Member

ananyo2012 commented Feb 2, 2017

@jywarren Yes just change them from warn to message. messages are shown with the 📖 icon instead of ⚠️

Also, this now makes the issue fail if not every one is completed

What do you mean by this? The tests are failing due to test failures not due to danger.

@jywarren
Copy link
Member Author

jywarren commented Feb 2, 2017

OK -- did so here: #1233

I'll double check this, sorry -- I may have overlooked it. But does warn not make tests fail? Just checking.

Thanks!

@jywarren
Copy link
Member Author

jywarren commented Feb 2, 2017

Great, thanks. Must have scrolled right past them!

@ananyo2012
Copy link
Member

No warn doesn't fail the build. there is another statement named fail to fail builds

@jywarren jywarren merged commit f561922 into publiclab:master Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants