= Integrity v22 http://github.com/integrity/integrity/compare/v21...v22 * New auto_branch feature. Say the project "Integrity" is tracking the master branch, and I push my "build-duration" topic branch to GitHub, Integrity will create and build a new project named "Integrity (build-duration)" using the same build command and notifiers * Remove the fork feature. I've found the auto_branch feature to be much more convenient * Populate commit meta data from the GitHub payload when receiving a push * Remove the /push endpoint in favor of GitHub-ish payloads * Improved build output colorization thanks to Ryan Tomayko's bcat. http://github.com/rtomayko/bcat * Improved GitHub links to compare view and commit page [Łukasz Strzałkowski, Simon Rozet] * Log git commands errors for easier troubleshooting * Upgrade to DataMapper 1.0 = Contact/Links Code http://github.com/integrity/integrity Docs http://integrityapp.com Bugs http://github.com/integrity/integrity/issues Chat irc://irc.freenode.net/integrity List integrity@librelist.com / http://librelist.com/browser/integrity/ -- github.com/sr
What about just dropping the per-project branches and changing the status display? On Tuesday, June 29, 2010, Simon Rozet <simon@rozet.name> wrote: > = Integrity v22 > > http://github.com/integrity/integrity/compare/v21...v22 > > * New auto_branch feature. Say the project "Integrity" is tracking the master > branch, and I push my "build-duration" topic branch to GitHub, Integrity > will create and build a new project named "Integrity (build-duration)" using > the same build command and notifiers > > * Remove the fork feature. I've found the auto_branch feature to be > much more convenient > > * Populate commit meta data from the GitHub payload when receiving a push > > * Remove the /push endpoint in favor of GitHub-ish payloads > > * Improved build output colorization thanks to Ryan Tomayko's bcat. > http://github.com/rtomayko/bcat > > * Improved GitHub links to compare view and commit page > [Łukasz Strzałkowski, Simon Rozet] > > * Log git commands errors for easier troubleshooting > > * Upgrade to DataMapper 1.0 > > = Contact/Links > > Code http://github.com/integrity/integrity > Docs http://integrityapp.com > Bugs http://github.com/integrity/integrity/issues > Chat irc://irc.freenode.net/integrity > List integrity@librelist.com / http://librelist.com/browser/integrity/ > > -- > github.com/sr >
Not sure what you mean. Are you saying it should be possible to track multiple branches under the same project? 2010/6/29 Nicolás Sanguinetti <hi@nicolassanguinetti.info>: > What about just dropping the per-project branches and changing the > status display? > > On Tuesday, June 29, 2010, Simon Rozet <simon@rozet.name> wrote: >> = Integrity v22 >> >> http://github.com/integrity/integrity/compare/v21...v22 >> >> * New auto_branch feature. Say the project "Integrity" is tracking the master >> branch, and I push my "build-duration" topic branch to GitHub, Integrity >> will create and build a new project named "Integrity (build-duration)" using >> the same build command and notifiers >> >> * Remove the fork feature. I've found the auto_branch feature to be >> much more convenient >> >> * Populate commit meta data from the GitHub payload when receiving a push >> >> * Remove the /push endpoint in favor of GitHub-ish payloads >> >> * Improved build output colorization thanks to Ryan Tomayko's bcat. >> http://github.com/rtomayko/bcat >> >> * Improved GitHub links to compare view and commit page >> [Łukasz Strzałkowski, Simon Rozet] >> >> * Log git commands errors for easier troubleshooting >> >> * Upgrade to DataMapper 1.0 >> >> = Contact/Links >> >> Code http://github.com/integrity/integrity >> Docs http://integrityapp.com >> Bugs http://github.com/integrity/integrity/issues >> Chat irc://irc.freenode.net/integrity >> List integrity@librelist.com / http://librelist.com/browser/integrity/ >> >> -- >> github.com/sr >> > -- github.com/sr
On Tue, Jun 29, 2010 at 3:57 PM, Simon Rozet <simon@rozet.name> wrote: > Not sure what you mean. Are you saying it should be possible to track > multiple branches under the same project? Yeah, why not? > 2010/6/29 Nicolás Sanguinetti <hi@nicolassanguinetti.info>: >> What about just dropping the per-project branches and changing the >> status display? >> >> On Tuesday, June 29, 2010, Simon Rozet <simon@rozet.name> wrote: >>> = Integrity v22 >>> >>> http://github.com/integrity/integrity/compare/v21...v22 >>> >>> * New auto_branch feature. Say the project "Integrity" is tracking the master >>> branch, and I push my "build-duration" topic branch to GitHub, Integrity >>> will create and build a new project named "Integrity (build-duration)" using >>> the same build command and notifiers >>> >>> * Remove the fork feature. I've found the auto_branch feature to be >>> much more convenient >>> >>> * Populate commit meta data from the GitHub payload when receiving a push >>> >>> * Remove the /push endpoint in favor of GitHub-ish payloads >>> >>> * Improved build output colorization thanks to Ryan Tomayko's bcat. >>> http://github.com/rtomayko/bcat >>> >>> * Improved GitHub links to compare view and commit page >>> [Łukasz Strzałkowski, Simon Rozet] >>> >>> * Log git commands errors for easier troubleshooting >>> >>> * Upgrade to DataMapper 1.0 >>> >>> = Contact/Links >>> >>> Code http://github.com/integrity/integrity >>> Docs http://integrityapp.com >>> Bugs http://github.com/integrity/integrity/issues >>> Chat irc://irc.freenode.net/integrity >>> List integrity@librelist.com / http://librelist.com/browser/integrity/ >>> >>> -- >>> github.com/sr >>> >> > > > > -- > github.com/sr >
Because it'd require much more changes ;-P 2010/6/29 Nicolás Sanguinetti <hi@nicolassanguinetti.info>: > On Tue, Jun 29, 2010 at 3:57 PM, Simon Rozet <simon@rozet.name> wrote: >> Not sure what you mean. Are you saying it should be possible to track >> multiple branches under the same project? > > Yeah, why not? > >> 2010/6/29 Nicolás Sanguinetti <hi@nicolassanguinetti.info>: >>> What about just dropping the per-project branches and changing the >>> status display? >>> >>> On Tuesday, June 29, 2010, Simon Rozet <simon@rozet.name> wrote: >>>> = Integrity v22 >>>> >>>> http://github.com/integrity/integrity/compare/v21...v22 >>>> >>>> * New auto_branch feature. Say the project "Integrity" is tracking the master >>>> branch, and I push my "build-duration" topic branch to GitHub, Integrity >>>> will create and build a new project named "Integrity (build-duration)" using >>>> the same build command and notifiers >>>> >>>> * Remove the fork feature. I've found the auto_branch feature to be >>>> much more convenient >>>> >>>> * Populate commit meta data from the GitHub payload when receiving a push >>>> >>>> * Remove the /push endpoint in favor of GitHub-ish payloads >>>> >>>> * Improved build output colorization thanks to Ryan Tomayko's bcat. >>>> http://github.com/rtomayko/bcat >>>> >>>> * Improved GitHub links to compare view and commit page >>>> [Łukasz Strzałkowski, Simon Rozet] >>>> >>>> * Log git commands errors for easier troubleshooting >>>> >>>> * Upgrade to DataMapper 1.0 >>>> >>>> = Contact/Links >>>> >>>> Code http://github.com/integrity/integrity >>>> Docs http://integrityapp.com >>>> Bugs http://github.com/integrity/integrity/issues >>>> Chat irc://irc.freenode.net/integrity >>>> List integrity@librelist.com / http://librelist.com/browser/integrity/ >>>> >>>> -- >>>> github.com/sr >>>> >>> >> >> >> >> -- >> github.com/sr >> > -- github.com/sr
What a Lazy Frenchie you turned out to be :P On Wed, Jun 30, 2010 at 12:36 PM, Simon Rozet <simon@rozet.name> wrote: > Because it'd require much more changes ;-P > > 2010/6/29 Nicolás Sanguinetti <hi@nicolassanguinetti.info>: >> On Tue, Jun 29, 2010 at 3:57 PM, Simon Rozet <simon@rozet.name> wrote: >>> Not sure what you mean. Are you saying it should be possible to track >>> multiple branches under the same project? >> >> Yeah, why not? >> >>> 2010/6/29 Nicolás Sanguinetti <hi@nicolassanguinetti.info>: >>>> What about just dropping the per-project branches and changing the >>>> status display? >>>> >>>> On Tuesday, June 29, 2010, Simon Rozet <simon@rozet.name> wrote: >>>>> = Integrity v22 >>>>> >>>>> http://github.com/integrity/integrity/compare/v21...v22 >>>>> >>>>> * New auto_branch feature. Say the project "Integrity" is tracking the master >>>>> branch, and I push my "build-duration" topic branch to GitHub, Integrity >>>>> will create and build a new project named "Integrity (build-duration)" using >>>>> the same build command and notifiers >>>>> >>>>> * Remove the fork feature. I've found the auto_branch feature to be >>>>> much more convenient >>>>> >>>>> * Populate commit meta data from the GitHub payload when receiving a push >>>>> >>>>> * Remove the /push endpoint in favor of GitHub-ish payloads >>>>> >>>>> * Improved build output colorization thanks to Ryan Tomayko's bcat. >>>>> http://github.com/rtomayko/bcat >>>>> >>>>> * Improved GitHub links to compare view and commit page >>>>> [Łukasz Strzałkowski, Simon Rozet] >>>>> >>>>> * Log git commands errors for easier troubleshooting >>>>> >>>>> * Upgrade to DataMapper 1.0 >>>>> >>>>> = Contact/Links >>>>> >>>>> Code http://github.com/integrity/integrity >>>>> Docs http://integrityapp.com >>>>> Bugs http://github.com/integrity/integrity/issues >>>>> Chat irc://irc.freenode.net/integrity >>>>> List integrity@librelist.com / http://librelist.com/browser/integrity/ >>>>> >>>>> -- >>>>> github.com/sr >>>>> >>>> >>> >>> >>> >>> -- >>> github.com/sr >>> >> > > > > -- > github.com/sr >