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
471409673,MDU6SXNzdWU0NzE0MDk2NzM=,3158,Out of date docstring for concat_dim in open_mfdataset,17169544,open,0,,,3,2019-07-23T00:01:05Z,2021-07-08T17:40:45Z,,CONTRIBUTOR,,,,"In the `open_mfdataset` [docstring](https://github.com/pydata/xarray/blob/f7e299f665dada1934e0f53d4294902103dcec74/xarray/backends/api.py#L608):

```
    concat_dim : str, or list of str, DataArray, Index or None, optional
        Dimensions to concatenate files along.  You only
        need to provide this argument if any of the dimensions along which you
        want to concatenate is not a dimension in the original datasets, e.g.,
        if you want to stack a collection of 2D arrays along a third dimension.
        ...
```

This is true for the default `combine='_old_auto'`, but when using `combine='nested'` it is required while it is not used by `combine='by_coords'`.  It would be clearer to make that distinction here.","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/3158/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,issue
467764970,MDExOlB1bGxSZXF1ZXN0Mjk3MzQ2NzYz,3113,[DOC] Be more explicit about netCDF groups and xarray.Dataset relationship.,17169544,closed,0,,,1,2019-07-13T20:48:58Z,2019-07-14T05:34:56Z,2019-07-14T05:34:56Z,CONTRIBUTOR,,0,pydata/xarray/pulls/3113,"This PR is related to the discussion in #2916.  In https://xarray.pydata.org/en/stable/io.html#netcdf there are statements like

>  netCDF files on disk directly correspond to Dataset objects.

This is useful conceptually but can be confusing when working with netCDF groups which are not supported as part of the data model.  I thought it would be clearer if the description of how to work with groups explicitly said this.","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/3113/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull
467741491,MDExOlB1bGxSZXF1ZXN0Mjk3MzMwMTA3,3110,Change name of testing conda environment,17169544,closed,0,,,5,2019-07-13T16:41:09Z,2019-07-13T17:12:30Z,2019-07-13T17:11:52Z,CONTRIBUTOR,,0,pydata/xarray/pulls/3110,"This PR changes the test environment name from `test_env` to `xarray-tests` for clarity and to be consistent with the documentation environment name (`xarray-docs`).

 - [x] Closes #3107 
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/3110/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull
467735590,MDU6SXNzdWU0Njc3MzU1OTA=,3107,The name of the conda environment in the contributing guide is generic,17169544,closed,0,,,3,2019-07-13T15:47:03Z,2019-07-13T17:11:51Z,2019-07-13T17:11:51Z,CONTRIBUTOR,,,,"In the [contributing guide](http://xarray.pydata.org/en/stable/contributing.html#creating-a-python-environment), you are instructed to make an environment `test_env`:

```
# Create and activate the build environment
conda env create -f ci/requirements/py36.yml
conda activate test_env

# or with older versions of Anaconda:
source activate test_env

# Build and install xarray
pip install -e . 
```

I think having the name be `xarray_test_env` would be clearer for people new to working with conda environments and using multiple projects.","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/3107/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,completed,13221727,issue
444510710,MDExOlB1bGxSZXF1ZXN0Mjc5MTU2MDI1,2964,Add fill_value for concat and auto_combine,17169544,closed,0,,,7,2019-05-15T15:40:48Z,2019-05-27T00:21:02Z,2019-05-27T00:20:55Z,CONTRIBUTOR,,0,pydata/xarray/pulls/2964,"This PR adds the optional `fill_value` parameter to `concat()` and `auto_combine()` in `xarray.core.combine`, plus the associated underlying functions in the module.  This builds on the previous PR #2920 in addressing issue #2876, and gives users the option to avoid type-changing to `float` for arrays with missing values when using these functions as discussed in issue #2870.

 - [x] Closes #2870
 - [x] Tests added
 - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/2964/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull
437418337,MDExOlB1bGxSZXF1ZXN0MjczNjk5NjUz,2920,"[WIP] Custom fill value for reindex, align, and merge operations",17169544,closed,0,,,5,2019-04-25T22:08:09Z,2019-05-05T20:31:58Z,2019-05-05T00:20:55Z,CONTRIBUTOR,,0,pydata/xarray/pulls/2920,"This PR adds an optional `fill_value` parameter for the following functions/methods:
```
xarray.core.alignment.align()
xarray.core.alignment.deep_align()

xarray.core.dataset.reindex()
xarray.core.dataset.reindex_like()
xarray.core.dataset.merge()

xarray.core.dataarray.DataArray.reindex()
xarray.core.dataarray.DataArray.reindex_like()

xarray.core.merge.merge_coords()
xarray.core.merge.merge_core()
xarray.core.merge.merge()
xarray.core.merge.dataset_merge_method()
```
The value given to `fill_value` is used to fill missing values in the new object after the operation.  By default `fill_value` is NaN.

 - [x] Closes #2876
 - [x] Tests added
 - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API
","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/2920/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull