issues: 1423972935
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 | 
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1423972935 | PR_kwDOAMm_X85BlCII | 7225 | join together duplicate entries in the text `repr` | 14808389 | closed | 0 | 4 | 2022-10-26T12:53:49Z | 2023-07-24T18:37:05Z | 2023-07-20T21:13:57Z | MEMBER | 0 | pydata/xarray/pulls/7225 | 
 
 The formatting options we were able to come up with:
1. separate with just newlines (see e29aeb9085bc677e16dabd4a2b94cf63d06c155e):
 For the unicode box components, we can choose between the light and heavy variants. @benbovy and I think the unicode variants (especially variant 3) are the easiest to understand, but we would need to decide whether we care about terminals that don't support unicode. Edit: in the meeting we decided that support for the subsection of unicode should be common enough that we can use it. I'll clean this PR up to implement option 3, then.  | 
                
                    {
    "url": "https://api.github.com/repos/pydata/xarray/issues/7225/reactions",
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
} | 
                
                    13221727 | pull |