issue_comments
4 rows where author_association = "MEMBER" and issue = 1623776623 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Added an introduction to the reshaping documentation · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1492125602 | https://github.com/pydata/xarray/pull/7623#issuecomment-1492125602 | https://api.github.com/repos/pydata/xarray/issues/7623 | IC_kwDOAMm_X85Y8Aei | TomNicholas 35968931 | 2023-03-31T15:26:10Z | 2023-03-31T15:26:10Z | MEMBER | Thanks @nishtha981 ! I just realised after merging that this PR should in theory have had a corresponding entry in the what's new page, as all PRs are supposed to have. We won't worry about that this time, but try and remember to add it next time! That way you will also be listed as a contributor on the what's new page. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Added an introduction to the reshaping documentation 1623776623 | |
1491278724 | https://github.com/pydata/xarray/pull/7623#issuecomment-1491278724 | https://api.github.com/repos/pydata/xarray/issues/7623 | IC_kwDOAMm_X85Y4xuE | TomNicholas 35968931 | 2023-03-31T04:40:58Z | 2023-03-31T04:40:58Z | MEMBER | I've also just told the readthedocs to rebuild just now |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Added an introduction to the reshaping documentation 1623776623 | |
1491278420 | https://github.com/pydata/xarray/pull/7623#issuecomment-1491278420 | https://api.github.com/repos/pydata/xarray/issues/7623 | IC_kwDOAMm_X85Y4xpU | TomNicholas 35968931 | 2023-03-31T04:40:23Z | 2023-03-31T04:40:23Z | MEMBER | Hi @nishtha981 - that's great that you identified what was causing the docs ci builds to fail! I was wondering why that was! Fixing this for xarray may require more than just re-running the ci. For example it might require us to pin a particular version of a library (here sphinx_book_theme) in order to guarantee the CI works again. If it doesn't work immediately now, what we normally do is to open a new github issue on xarray's issue tracker to track the problem. That way if the problem comes up in multiple PRs we can just refer all of them back to the one issue, until it gets resolved completely. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Added an introduction to the reshaping documentation 1623776623 | |
1490687686 | https://github.com/pydata/xarray/pull/7623#issuecomment-1490687686 | https://api.github.com/repos/pydata/xarray/issues/7623 | IC_kwDOAMm_X85Y2hbG | TomNicholas 35968931 | 2023-03-30T17:43:55Z | 2023-03-30T17:43:55Z | MEMBER | I've made a final edit to remove the mention of a specific method in the intro, and remove some blanks lines. This looks good to me now so I'll merge it! Thanks @nishtha981 ! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Added an introduction to the reshaping documentation 1623776623 |
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, [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]);
user 1