pull_requests: 799209108
This data as json
id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
799209108 | PR_kwDOAMm_X84vovaU | 6056 | closed | 0 | add set_options link to FAQ on metadata | 3698640 | If helpful - added a PR to adds a reference and link to `xr.set_options` in the section of the FAQ on "what is your approach to metadata?". I had to do a bit of digging to figure out what was meant by "there is a global flag" and thought others might find the direct ref useful. Relevant section: https://github.com/pydata/xarray/blob/main/doc/getting-started-guide/faq.rst#what-is-your-approach-to-metadata Current text: > An implication of this choice is that we do not propagate ``attrs`` through most operations unless explicitly flagged (some methods have a ``keep_attrs`` option, and there is a global flag for setting this to be always True or False) Proposed version: > An implication of this choice is that we do not propagate ``attrs`` through most operations unless explicitly flagged (some methods have a ``keep_attrs`` option, and there is a global flag, **accessible with [`xr.set_options`](http://xarray.pydata.org/en/stable/generated/xarray.set_options.html),** for setting this to be always True or False). Minor docs change only. No workflow steps needed. | 2021-12-09T21:04:21Z | 2021-12-15T06:21:18Z | 2021-12-09T21:39:45Z | 2021-12-09T21:39:45Z | 8073a7f84d57d06fd162840bbe827d9eab729156 | 0 | 599875b3db6f95e28e097a1e8086323e9e12fb67 | a9238339f55edac0f2efb4a231c8818c5539bd28 | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/6056 |
Links from other tables
- 1 row from pull_requests_id in labels_pull_requests