[ckan-dev] Github Issues

Sat Jan 12 04:09:25 UTC 2013

On 11 January 2013 13:29, Sean Hammond <sean.hammond at okfn.org> wrote:

> > I've created a quick and dirty script to link pull requests and issues.
> >
> > Currently it assumes you are in a branch called xxx-.... where xxx is the
> > same number as the issue it relates to.
> > let me know of any problems/suggestions
> >
> > https://github.com/tobes/gitlink
>
> Do we really need to make existing issues into pull requests or can we
> just create new pull requests? I know it's nice to have just one issue
> instead of two but it's a PITA since the web interface doesn't do it,
> and I did notice that if you refer to an issue from a commit or pull
> request then it automatically puts links to the commits and pull request
> in the issue:
>
> https://github.com/okfn/ckan/issues/268
>
> so we won't lose track of which pull requests are for which issues.
>
> Just use the original issue number (and not the new issue number from
> the pull request) in your branch names and commit messages.
>
>
I think it is nice to have the pull request with the issue.  yeah it sucks
that you can't do this from the web interface but it is easy using my
wonderful script or that hub thing if you are that way inclined.  It keeps
the number of issues down too. on just feels easier to manage.

I think the most important thing is to keep revisiting how we use github
every couple of weeks or so till we develop a best approach
and discover it's charms and pitfalls and we get some consistency of use

It's kind of equivalent to with trac, we'd have a trac issue and a
> github pull request and reference between them manually
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130112/81f42171/attachment-0001.html>