From: Puneeth Chaganti <punchagan@gmail.com>
To: William Henney <whenney@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Announce] A GitHub Issues interface for Org-mode
Date: Thu, 2 Jun 2011 06:11:08 +0530 [thread overview]
Message-ID: <BANLkTinVzW4EOXCeyxJs6+HYb4qTQV30ZQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimBZNKJXO0K_MC1s3_1oWeOOTM+=A@mail.gmail.com>
Hi William,
On Mon, May 30, 2011 at 8:08 PM, William Henney <whenney@gmail.com> wrote:
[..]
> Is the v2 API missing some features you need? Maybe it would be better
> to use that until v3 is out of beta
v2 API doesn't provide access to the new features of Issues, added in
version 2 of GitHub Issues, like Milestones. I thought adding the
Milestone due date as a deadline would be useful. But, as you suggest,
I should probably try things with APIv2 until the v3 is more stable.
[..]
> Well, the wiping of text directly below an issue's level 2 heading is
> a data-loss bug, so I would suggest that you certainly don't do that
> :)
Yes. I'll fix it, as soon as I get some time and am able to move stuff to v2.
> With respect to sub-headings (level 3 or below) that are added by hand
> to the github.org file, I would suggest that by default you do not
> sync them with GitHub. Maybe you could have a function called
> something like org-ghi-make-heading-a-comment that would work in a
> similar way to org-ghi-make-todo-an-issue. However, it seems that
> GitHub issue comments only understand markdown syntax, not org syntax,
> so unless the comment is just simple text it would require an export
> step (https://github.com/alexhenning/ORGMODE-Markdown might help
> there).
Thanks for the suggestions, will look into them. :)
--
Puneeth
prev parent reply other threads:[~2011-06-02 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 4:40 [Announce] A GitHub Issues interface for Org-mode Puneeth Chaganti
2011-05-30 3:46 ` William Henney
2011-05-30 4:43 ` Puneeth Chaganti
2011-05-30 14:38 ` William Henney
2011-06-02 0:41 ` Puneeth Chaganti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinVzW4EOXCeyxJs6+HYb4qTQV30ZQ@mail.gmail.com \
--to=punchagan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=whenney@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).