home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

1 row where issue = 1118974427 and user = 35968931 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • TomNicholas · 1 ✖

issue 1

  • update HOW_TO_RELEASE.md · 1 ✖

author_association 1

  • MEMBER 1
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1026138477 https://github.com/pydata/xarray/pull/6214#issuecomment-1026138477 https://api.github.com/repos/pydata/xarray/issues/6214 IC_kwDOAMm_X849KaFt TomNicholas 35968931 2022-01-31T19:38:19Z 2022-01-31T19:38:19Z MEMBER

Insert things like contributors automatically; I've used fastmod for this sort of automation Not sure whether we can strip out bot names?

Yes, let's do that - we could have a bot name red list, but I don't personally think it matters if there are a couple of bot names or duplicated names in the list.

Automate checks for things like "am I on the correct branch", remove checks like "run the tests again" given our CI infra is really good now

If we can do this reliably then yes!

Automate release notes? Is this possible (without spinning up GPT3 :) ) I didn't add a description for them the most recent release We already have whatsnew, maybe that's enough? I rather enjoy reading release notes for libraries I follow! So maybe this is something to spend a few minutes on?

I feel like we could just make release notes explicitly optional? So we can write a summary if there is particularly cool feature we want to highlight, but most of the time the whatsnew will do fine?

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  update HOW_TO_RELEASE.md 1118974427

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

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,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);
Powered by Datasette · Queries took 51.489ms · About: xarray-datasette