label set / issue closed dates

[zzzeek]

Hey there !

Since you used my project as an example I'm still toying with actually using this for said project (SQLAlchemy).

I'm trying to figure out where githubs API is documented for this, I see the gist at https://gist.github.com/jonmagic/5282384165e0f86ef105 but that's two years old....

Anyway if you look at an issue all the labels and the "closed' status say "closed just now" rather than "closed six years ago" as it should for an old issue. Sorry I'm coming late to this and if you'd rather I figure this all out myself I can do that but it looks like there is a least a "closed_at" date that can be added?

is this still a "pending" API that github is going to announce?

[jeffwidman]

Sorry @zzzeek, been sick so been slow to respond.

I did most of my migrations two years ago, so haven't checked with GitHub whether there's a newer API since then... I have a feeling this API will permanently be in "beta" status. If you're aware of a newer endpoint, I'm happy to update this code.

Also, for a repo the size of SQLAlchemy, you'll want to be aware of #85 (which we can fix) and #65 which appears to be a bug within GitHub that is difficult to consistently reproduce externally: #65 (comment).

So you should probably expect to a few failures before you get a successful migration.

IIRC, you use Gerrit for SQLAlachemy which I hear is like vim, powerful but a steep learning curve, so I'm curious if GitHub issues would be used in parallel with Gerrit or as a replacement for Gerrit?

Lastly, have you considered migrating issues to Gitlab? Less developer mindshare, but I think they're a viable contender for certain projects. Three things they have over GitHub are supporting attaching files to issues, open-core so can hack in a feature that you want, and tight integration with test runners etc as part of the repo toolset. But lack of developer mindshare/familiarity is a big price to pay for popular open-source projects.