issues: 1422482990
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1422482990 | PR_kwDOAMm_X85BgEYZ | 7212 | use the new action to create an issue from the output of reportlog | 14808389 | closed | 0 | 0 | 2022-10-25T13:37:42Z | 2022-10-26T09:34:09Z | 2022-10-26T09:12:42Z | MEMBER | 0 | pydata/xarray/pulls/7212 | I'm not sure if we actually need the dedicated "report" job, or whether adding an additional step to the main ci job would suffice? I can see two reasons for a separate job: 1. we get to control the python version independently from the version of the main job 2. we upload the reportlog files as artifacts I think if we can change the action to abort if it is run on a python version it does not support the first concern would not matter anymore, and for 2 we might just keep the "upload artifact" action (but is it even possible to manually access artifacts? If not we might not even need the upload). Since I don't think either is a major concern, I went ahead and joined the jobs.
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/7212/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |