issue_comments
11 rows where author_association = "OWNER", "created_at" is on date 2020-02-23 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 11 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
590113889 | https://github.com/simonw/datasette/issues/676#issuecomment-590113889 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU5MDExMzg4OQ== | simonw 9599 | 2020-02-23T20:44:11Z | 2020-02-23T20:44:11Z | OWNER | Still needs documentation before I can land it in master. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_searchmode=raw option for running FTS searches without escaping characters 568091133 | |
590113869 | https://github.com/simonw/datasette/issues/676#issuecomment-590113869 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU5MDExMzg2OQ== | simonw 9599 | 2020-02-23T20:43:59Z | 2020-02-23T20:43:59Z | OWNER | You can try this right now like so:
Then use the following:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_searchmode=raw option for running FTS searches without escaping characters 568091133 | |
590110086 | https://github.com/simonw/datasette/issues/676#issuecomment-590110086 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU5MDExMDA4Ng== | simonw 9599 | 2020-02-23T20:06:03Z | 2020-02-23T20:06:52Z | OWNER | Nice thing about the "search mode" concept is that I can optionally reflect it in the HTML UI in some way - maybe with a checkbox for "raw" mode that only shows up if the user hits the page with It also hints at potentially adding further search modes in the future. Not sure if I'd do that but it's an interesting potential avenue to explore. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_searchmode=raw option for running FTS searches without escaping characters 568091133 | |
590109778 | https://github.com/simonw/datasette/issues/676#issuecomment-590109778 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU5MDEwOTc3OA== | simonw 9599 | 2020-02-23T20:02:28Z | 2020-02-23T20:02:28Z | OWNER |
I could go with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_searchmode=raw option for running FTS searches without escaping characters 568091133 | |
590109450 | https://github.com/simonw/datasette/issues/676#issuecomment-590109450 | https://api.github.com/repos/simonw/datasette/issues/676 | MDEyOklzc3VlQ29tbWVudDU5MDEwOTQ1MA== | simonw 9599 | 2020-02-23T19:59:11Z | 2020-02-23T19:59:11Z | OWNER | I'm going to call it |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
?_searchmode=raw option for running FTS searches without escaping characters 568091133 | |
590107843 | https://github.com/simonw/datasette/issues/681#issuecomment-590107843 | https://api.github.com/repos/simonw/datasette/issues/681 | MDEyOklzc3VlQ29tbWVudDU5MDEwNzg0Mw== | simonw 9599 | 2020-02-23T19:42:15Z | 2020-02-23T19:42:15Z | OWNER | Those security headers from your screenshot are definitely worth me thinking more about. Even if not as core features they could make a great officially supported plugin. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Cashe-header missing in http-response 569317377 | |
590107464 | https://github.com/simonw/datasette/issues/681#issuecomment-590107464 | https://api.github.com/repos/simonw/datasette/issues/681 | MDEyOklzc3VlQ29tbWVudDU5MDEwNzQ2NA== | simonw 9599 | 2020-02-23T19:38:16Z | 2020-02-23T19:38:16Z | OWNER | The |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Cashe-header missing in http-response 569317377 | |
590107309 | https://github.com/simonw/datasette/issues/681#issuecomment-590107309 | https://api.github.com/repos/simonw/datasette/issues/681 | MDEyOklzc3VlQ29tbWVudDU5MDEwNzMwOQ== | simonw 9599 | 2020-02-23T19:36:33Z | 2020-02-23T19:36:33Z | OWNER | For adding extra HTTP headers I suggest writing a plugin. There's an example in the docs of one that adds a simple HTTP header here: https://datasette.readthedocs.io/en/stable/plugins.html#asgi-wrapper-datasette You don't need to bundle it up as a full Python package - you can create a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Cashe-header missing in http-response 569317377 | |
590106416 | https://github.com/simonw/datasette/issues/680#issuecomment-590106416 | https://api.github.com/repos/simonw/datasette/issues/680 | MDEyOklzc3VlQ29tbWVudDU5MDEwNjQxNg== | simonw 9599 | 2020-02-23T19:26:40Z | 2020-02-23T19:26:40Z | OWNER | I think this should go a step further: I'd like some extra tests that run when a new build is being shipped and confirm that it has release notes in the right place. So this is a Travis CI responsibility. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release automation: automate the bit that posts the GitHub release 569275763 | |
590030425 | https://github.com/simonw/datasette/issues/680#issuecomment-590030425 | https://api.github.com/repos/simonw/datasette/issues/680 | MDEyOklzc3VlQ29tbWVudDU5MDAzMDQyNQ== | simonw 9599 | 2020-02-23T05:53:48Z | 2020-02-23T05:53:48Z | OWNER | For the actual implementation: I think this is a GitHub Action. It looks for new tags, and when a tag is created it builds the docs using Sphinx, extracts the latest HTML changelog entry using BeautifulSoup, cleans it up a bit (I think the only thing that needs doing is turning relative links into absolute ones), runs it through pypandoc to create https://developer.github.com/v3/repos/releases/#create-a-release |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release automation: automate the bit that posts the GitHub release 569275763 | |
590030258 | https://github.com/simonw/datasette/issues/680#issuecomment-590030258 | https://api.github.com/repos/simonw/datasette/issues/680 | MDEyOklzc3VlQ29tbWVudDU5MDAzMDI1OA== | simonw 9599 | 2020-02-23T05:51:04Z | 2020-02-23T05:51:04Z | OWNER | Did a bunch of research in a Jupyter notebook and it looks like I can use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Release automation: automate the bit that posts the GitHub release 569275763 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [issue] INTEGER REFERENCES [issues]([id]) , [performed_via_github_app] TEXT); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
issue 3