Skip to contentSkip to conversation

git-bugzilla

DISCUSSION Steve Frécinaux 2 participants 2 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi folks,

Here is a chunk of code I wrote a few time ago, to post patches to bugzilla, modelled mostly after git-format-patch/git-send-email.

You can find it there:
http://code.istique.net/?p=git-bugzilla.git

It is written in perl and requires WWW::Mechanize.

Hope you like it.

Here is an excerpt of the man page:

NAME
----
git-send-bugzilla - Attach patches to a bugzilla bug

SYNOPSIS
--------
'git-send-bugzilla' [OPTIONS] (--dry-run | <bugid>)

                    <since>[..<until>]

DESCRIPTION
-----------

Attach each commit between <since> and <until> to the bug <bugid> on GNOME's bugzilla.
If ..<until> is not specified, the head of the current working tree is implied.

If -n (or bugzilla.numbered in the repository configuration) is specified, instead of "[PATCH] Subject", the first line is formatted as "[n/m] Subject".

OPTIONS
-------
-b|--url <url>::
The Bugzilla URL.

-u|--username <username>::
Your Bugzilla user name.

-p|--password <password>::
Your Bugzilla password.

-s|--squash::
Send all the selected commits as a single patch.

-n|--numbered::
Prefix attachment names with [n/m].

--start-number <n>::
Start numbering the patches at <n> instead of 1.

--dry-run::
Don't do anything for real. If you use this option you shouldn't specify a bug id.

EXAMPLES
--------
git-send-bugzilla -n 12345 master
Extract all commits which are in the current branch but not in the 'master' branch. Each commit will be attached as a single patch to the bug #12345