issue_comments

Table actions

5 rows where issue = 873842812 and user = 14808389 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 1

  • keewis · 5 ✖

issue 1

  • Add GitHub action for publishing artifacts to PyPI · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
833593243 https://github.com/pydata/xarray/pull/5244#issuecomment-833593243 https://api.github.com/repos/pydata/xarray/issues/5244 MDEyOklzc3VlQ29tbWVudDgzMzU5MzI0Mw== keewis 14808389 2021-05-06T15:00:32Z 2021-05-06T15:00:32Z MEMBER

it seems PyPI does not allow packages with versions like 0.17.1.dev108+gf5e4fd5f. I'm not sure if it's possible to have setuptools-scm create a different version. Should we run this only when a tag is created?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add GitHub action for publishing artifacts to PyPI 873842812
833541994 https://github.com/pydata/xarray/pull/5244#issuecomment-833541994 https://api.github.com/repos/pydata/xarray/issues/5244 MDEyOklzc3VlQ29tbWVudDgzMzU0MTk5NA== keewis 14808389 2021-05-06T13:53:27Z 2021-05-06T13:53:27Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add GitHub action for publishing artifacts to PyPI 873842812
833523795 https://github.com/pydata/xarray/pull/5244#issuecomment-833523795 https://api.github.com/repos/pydata/xarray/issues/5244 MDEyOklzc3VlQ29tbWVudDgzMzUyMzc5NQ== keewis 14808389 2021-05-06T13:29:18Z 2021-05-06T13:29:18Z MEMBER

should make sure to get the necessary tokens from PyPI and TestPyPI

I grabbed the xarray name on TestPyPI so TESTPYPI_TOKEN is already set

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add GitHub action for publishing artifacts to PyPI 873842812
832591142 https://github.com/pydata/xarray/pull/5244#issuecomment-832591142 https://api.github.com/repos/pydata/xarray/issues/5244 MDEyOklzc3VlQ29tbWVudDgzMjU5MTE0Mg== keewis 14808389 2021-05-05T10:43:49Z 2021-05-05T10:43:49Z MEMBER

from #5232:

@kmuehlbauer

Why not always upload pushes to master to test.pypi.org?

@andersy005, what do you think? This should be pretty easy if we have separate jobs for building / testing / uploads (where the upload to pypi is skipped unless a release was created)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add GitHub action for publishing artifacts to PyPI 873842812
831511929 https://github.com/pydata/xarray/pull/5244#issuecomment-831511929 https://api.github.com/repos/pydata/xarray/issues/5244 MDEyOklzc3VlQ29tbWVudDgzMTUxMTkyOQ== keewis 14808389 2021-05-03T20:25:32Z 2021-05-03T20:25:32Z MEMBER

if it's possible, it might still make sense to create and test the wheels for uploaded v0.x.y tags in a job and only upload to PyPI if a release was created through the webpage (which would save us from re-creating a release if the build failed).

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add GitHub action for publishing artifacts to PyPI 873842812

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]);