home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

4 rows where issue = 663287119 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

  • max-sixty 2
  • rpgoldman 1
  • keewis 1

author_association 2

  • MEMBER 3
  • CONTRIBUTOR 1

issue 1

  • Clarify drop_vars return value. · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
674273118 https://github.com/pydata/xarray/pull/4244#issuecomment-674273118 https://api.github.com/repos/pydata/xarray/issues/4244 MDEyOklzc3VlQ29tbWVudDY3NDI3MzExOA== max-sixty 5635139 2020-08-14T21:09:00Z 2020-08-14T21:09:00Z MEMBER

I realize that we may have lost a sentence through the merges; maybe someone clicked on apply suggestion to apply my suggestion. To the extent that wasn't your intention @rpgoldman lmk and I'll add back

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Clarify drop_vars return value. 663287119
663970583 https://github.com/pydata/xarray/pull/4244#issuecomment-663970583 https://api.github.com/repos/pydata/xarray/issues/4244 MDEyOklzc3VlQ29tbWVudDY2Mzk3MDU4Mw== keewis 14808389 2020-07-26T10:27:04Z 2020-07-26T10:27:04Z MEMBER

Any idea why the docs build failed?

that has been fixed in #4254 so merging master should be enough.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Clarify drop_vars return value. 663287119
663931037 https://github.com/pydata/xarray/pull/4244#issuecomment-663931037 https://api.github.com/repos/pydata/xarray/issues/4244 MDEyOklzc3VlQ29tbWVudDY2MzkzMTAzNw== rpgoldman 3274 2020-07-26T03:29:18Z 2020-07-26T03:29:18Z CONTRIBUTOR

Thanks @rpgoldman !

What do you think of that change? Feel free to discard if you disagree and we'll merge your initial suggestion.

How about we keep your sentence which is much better than my first sentence, and my second sentence? I think it's important to make the point that this function does not have side effects.

Any idea why the docs build failed?

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Clarify drop_vars return value. 663287119
663914679 https://github.com/pydata/xarray/pull/4244#issuecomment-663914679 https://api.github.com/repos/pydata/xarray/issues/4244 MDEyOklzc3VlQ29tbWVudDY2MzkxNDY3OQ== max-sixty 5635139 2020-07-25T23:03:02Z 2020-07-25T23:03:02Z MEMBER

Thanks @rpgoldman !

What do you think of that change? Feel free to discard if you disagree and we'll merge your initial suggestion.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Clarify drop_vars return value. 663287119

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 16.96ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows