issues, extensions and bitbucket

[Sean Farley]

Uwe Brauer <oub at mat.ucm.es> writes:

>     > Uwe Brauer <oub at mat.ucm.es> writes:
>
>
>     > :-)
>
>
>     > Our issues api has some warts for sure. Luckily, I can work on that side
>     > if the need is there (and my time allows).
>
>
>     > I don't know what format you want as output but it's pretty simple to
>
> Well artemis uses basically the good old unix mbox format. Here is a
> typical one
>
>
> From: Uwe Brauer  <oub at mat.ucm.es>
> Date: Fri, 07 Jul 2017 09:09:47 +0000
> State: new
> Subject: The function org-table-import-xlsx-to-csv-org returns an error message
> Message-Id: <baa2557804d4cbaa-0-artemis at Gilgamesch>
>
> And any comment on that issue is a mbox file as well.

Fair enough.

>     > read the json in python and output whatever you want. For instance, if
>     > you want to get all your issues that are tasks:
>
> Ok I will try this out later. Another approach is that bitbucket would
> support the artemis extension :-D maybe creating a say 'poor-man' issue system,
> no insult intended!

Well, one of the reasons we wrote the api the way we did (but still have
work to do to improve it) is so that developers can write their own
extensions :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20170710/72143176/attachment.asc>