issue_comments: 391055490
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/simonw/datasette/pull/279#issuecomment-391055490 | https://api.github.com/repos/simonw/datasette/issues/279 | 391055490 | MDEyOklzc3VlQ29tbWVudDM5MTA1NTQ5MA== | 9599 | 2018-05-22T16:29:30Z | 2018-05-22T16:29:30Z | OWNER | This is fantastic! I think I prefer the aesthetics of just "0.22" for the version string if it's a tagged release with no additional changes - does that work? I'd like to continue to provide a tuple that can be imported from the version.py module as well, as seen here: https://github.com/simonw/datasette/blob/558d9d7bfef3dd633eb16389281b67d42c9bdeef/datasette/version.py#L1 Presumably we can generate that from the versioneer string? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | 325352370 |