That is exactly the goal of my pull request at https://github.com/sympy/sympy-bot/pull/123. I've given an example of a before and after: https://github.com/sympy/sympy-bot/pull/123#issuecomment-7475278.
Perhaps we should upload even that info to the reviews site, and only actually post one line on the PR as you suggest. That would be a little bit more work, though (I'm personally not up to it right now, but patches welcome). Aaron Meurer On Wed, Aug 8, 2012 at 4:17 PM, Jason Moore <[email protected]> wrote: > What about reducing the length of the SymPy bot's post in the conversation > on the PR? I think the travisbot is a one liner. The test results can be > found by click the link in the one line. > > Example > > SymPy bot test fails 32 tests, [details are here]. > > Jason > > > On Wednesday, August 8, 2012 3:02:49 PM UTC-7, Aaron Meurer wrote: >> >> I actually think that the bots are useful for these. It's basically >> free test running for your code, meaning you can find and fix bugs >> sooner in the development process. >> >> Aaron Meurer >> >> On Wed, Aug 8, 2012 at 2:47 PM, Jason Moore <[email protected]> wrote: >> > I like the work in progress idea (WIP). The github pull request >> > conversation >> > view is a really nice way to talk about code with someone, regardless if >> > it >> > is ready to be merged into the stable branch or not. Github's internal >> > workflow uses a pull early model: >> > http://scottchacon.com/2011/08/31/github-flow.html . It would be nice if >> > we >> > could turn off the bots for WIP (early pulls) so that they don't clutter >> > the >> > conversation. Is that possible? Who is controlling the bots, or is it >> > all >> > automated? The bots stress me out when the pull request is young and >> > still >> > needs a lot of work and they don't provide that much useful information. >> > >> > Jason >> > >> > >> > On Wednesday, August 8, 2012 2:23:38 AM UTC-7, smichr wrote: >> >> >> >> I only ever rebase, and the only thing I have to watch out for is to >> >> not extend acbk into master's commits, e.g. `git rebase -i head~5` to >> >> work with the last 5 commits *of mine*. If the 6th one is a merge that >> >> is part of master then that can be really nasty (it shows up as there >> >> being more than 6 commits that you are working with in the editor -- >> >> that's how I know if I made a counting error). >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "sympy" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/sympy/-/1PcG3Mh2hQUJ. >> > >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]. >> > For more options, visit this group at >> > http://groups.google.com/group/sympy?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/sympy/-/_WSxjcria2IJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
