Skip to content

First stab at automated comments #208

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

Merged
merged 29 commits into from
Apr 29, 2015
Merged

First stab at automated comments #208

merged 29 commits into from
Apr 29, 2015

Conversation

cpsievert
Copy link
Collaborator

Once completed, this will close #207

@cpsievert
Copy link
Collaborator Author

@cpsievert
Copy link
Collaborator Author

Commit ab1967e was successfully merged with fafbff9 (master) to create d55e200. A visual testing table comparing fafbff9 with d55e200
http://ropensci.github.io/plotly-test-table/tables/d55e2001c32059f90f963c63db213267c54fe63f/index.html

@cpsievert
Copy link
Collaborator Author

Well, this ended up being more work than I anticipated...

Note that the "dev" branch in the testing table should now reflect results after merging with master. I think this is a safer/better/right approach (new behavior could sneak in after merging)

@chriddyp @mkcor @tdhock please review and let me know if you have any ideas for other comments/links that you’d like to be automatically posted.

@mkcor
Copy link
Contributor

mkcor commented Apr 28, 2015

What do you call the "dev" branch? Do you mean the feature branch? There is no dev branch in continuous integration (https://github.com/ropensci/plotly/wiki/Development-guidelines#contributors-guide). 🐤

Reviewing now. Thanks for submitting, @cpsievert

@cpsievert
Copy link
Collaborator Author

yea, I meant feature (not dev) branch

@mkcor
Copy link
Contributor

mkcor commented Apr 28, 2015

Wow, very impressive! 💨

Ideally I would like to see these messages as posted by bot so it's clearer that they are automated.

Good point on merging with master to see the actual final resulting images.

Regarding the comment, maybe I would prefix it with something like "in the testing environment", otherwise a quick read might seem scary, like "Commit ab1967e was successfully merged into master..." wait, what?

@cpsievert
Copy link
Collaborator Author

Thanks @mkcor 😊

Good point about the comment, maybe I'll just prefix with "On Travis, ..."?

I agree it'd be nice to have these messages posted by a "bot". Unfortunately, I think that means we'll have to create a new user and grant it write access to this repo...

@chriddyp
Copy link
Member

wow, pretty sweet!

@cpsievert
Copy link
Collaborator Author

Hold on, I might be able to create an organization that can post comments...

@cpsievert
Copy link
Collaborator Author

Hmm, it seems as though I'd have to register a web application to post comments via an organization which seems like overkill (not to mention more complicated). I suppose I could create a new user, but someone (Karthik?) would have to grant write access to that user...

@mkcor
Copy link
Contributor

mkcor commented Apr 28, 2015

@cpsievert It might not be worth the trouble, indeed. Then maybe the comment can start with this line

-----BEGIN BOT MESSAGE-----

and end with

-----END BOT MESSAGE-----

to catch our visual attention, and it's no big deal to have it posted by 'you'.

👍 for "On Travis, ..."

@cpsievert
Copy link
Collaborator Author

The message below was automatically generated after build https://travis-ci.org/ropensci/plotly/builds/60474246

On TravisCI, commit f3b40a7 was successfully merged with fafbff9 (master) to create df4f336. A visual testing table comparing fafbff9 with df4f336 can be found here:
http://ropensci.github.io/plotly-test-table/tables/df4f3366f07a834ece8d8ace6602d60e6b2584c7/index.html

@cpsievert
Copy link
Collaborator Author

OK, I think I'm happy with the format of the comment now. Feel free to let me know what you think!

@mkcor
Copy link
Contributor

mkcor commented Apr 29, 2015

Getting really stylish!
All good. 👍

cpsievert added a commit that referenced this pull request Apr 29, 2015
First stab at automated comments
@cpsievert cpsievert merged commit d9ecaf4 into master Apr 29, 2015
@cpsievert cpsievert deleted the bot branch April 29, 2015 03:21
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.

post a comment after building test table
3 participants