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
1215946244,PR_kwDOAMm_X842zRtP,6515,Add allow_failures flag to Dataset.curve_fit,11289391,closed,0,,,4,2022-04-26T13:17:18Z,2023-06-16T03:15:09Z,2023-06-16T03:15:09Z,CONTRIBUTOR,,0,pydata/xarray/pulls/6515,"- [x] Closes #6317
- [ ] Tests added
- [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst`

For some reason, my grepping doesn't seem to show any existing tests for `curve_fit`...?","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/6515/reactions"", ""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 1}",,,13221727,pull
1092546388,PR_kwDOAMm_X84weBgE,6132,"Check for just `...`, rather than `[...]` in `da.stack`",11289391,closed,0,,,3,2022-01-03T14:13:28Z,2022-01-04T04:57:12Z,2022-01-03T23:05:23Z,CONTRIBUTOR,,0,pydata/xarray/pulls/6132,"- [x] Closes #6051
- [x] Tests added
- [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - not quite just yet, as I'm not 100% sure in what category you'd put it!

`_stack_once` seemed like a reasonable place to put this check, just going from the trace of where the test failed. 

I also saw mypy failures during the local pre-commit step, but chose to ignore them for now given #6024. They seemed to pop up in unrelated areas, anyway.","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/6132/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull