During the last meeting, there was some discussion about having the ability to close tasks related to port improvements as part of a post commit hook in git. Essentially a CLI client for flyspray. I've started hacking something together that does just that, I have dubbed the project clispray[1][2]. It's functionality is pretty basic at the moment, it can login, logout and close tasks. If this is something the dev community likes, I'll work on it some more. [1] http://git.die.net.au/cgit/crux/tools/clispray [2] git://git.die.net.au/crux/tools/clispray -- Lucas Hazel <lucas@die.net.au>
Hi Lucas, On Thu, Jul 10, 2008 at 22:02:54 +1000, Lucas Hazel wrote:
During the last meeting, there was some discussion about having the ability to close tasks related to port improvements as part of a post commit hook in git. Essentially a CLI client for flyspray.
I've started hacking something together that does just that, I have dubbed the project clispray[1][2].
It's functionality is pretty basic at the moment, it can login, logout and close tasks. If this is something the dev community likes, I'll work on it some more.
I like it a lot, both the idea and the code. I'd also like to see this in our git repo soon :-). I've mentioned a couple of ideas in the meeting notes as well, but I think this will offer many nice possibilities; IRC integration might be nice, so that one could run @FSQUERY 200 -> <description> <state> Just thinking outloud here ;-) As for directly closing bugs via git commit message, what would be a good format? "[fixes FS#123]" ? Does anyone know whether we can have URLs in flyspray's comments to point directly to the commit in gitweb? Thanks, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
Hello, Johannes. On Fri, 11 Jul 2008 09:45:39 +0200 Johannes Winkelmann <jw@smts.ch> wrote:
[...] As for directly closing bugs via git commit message, what would be a good format? "[fixes FS#123]" ?
Does anyone know whether we can have URLs in flyspray's comments to point directly to the commit in gitweb?
Thanks, Johannes
At least We can have FS tickets mentioned in git commit messages. Here is a part of my conversation with the person behind Archlinux web setup: On Sat, 19 Apr 2008 15:59:04 -0700 eliott <xxxxxx@xxx.xx> wrote:
[...] It is just a small modification to gitweb that makes the links show up as they do. We have more of a process, when you make a commit message you specify FS#111
The FS#<int> then becomes a link to the flyspray ticket of that number.
code: http://code.cactuswax.net/git/?p=gitweb.git;a=blob;f=gitweb.cgi.patch;h=2043...
example usage: http://code.cactuswax.net/git/?p=gitweb.git;a=blob;f=gitweb-patch-info.txt;h...
We don't have any automated hooks or anything like that.
Here is a working gitweb example: http://projects.archlinux.org/gitweb.cgi?p=pacman.git;a=commit;h=ab506f77c04... -- Mikhail Kolesnik ICQ: 260259143 IRC: mike_k at freenode/#crux, rusnet/#yalta
participants (3)
-
Johannes Winkelmann -
Lucas Hazel -
Mikhail Kolesnik