html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/826#issuecomment-210710788,https://api.github.com/repos/pydata/xarray/issues/826,210710788,MDEyOklzc3VlQ29tbWVudDIxMDcxMDc4OA==,4295853,2016-04-16T01:56:41Z,2016-04-16T01:56:41Z,CONTRIBUTOR,"Thanks @shoyer! I think after this discussion that this is something we should handle within our own wrapper.  There does not seem to be a clean one size fits all solution warranting inclusion in xarray, unless I'm mistaken. If so, I hope someone chimes in to correct me.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,148771214
https://github.com/pydata/xarray/issues/826#issuecomment-210683210,https://api.github.com/repos/pydata/xarray/issues/826,210683210,MDEyOklzc3VlQ29tbWVudDIxMDY4MzIxMA==,4295853,2016-04-15T23:32:03Z,2016-04-15T23:32:03Z,CONTRIBUTOR,"Thanks @shoyer.  Is the fundamental issue code boat or is the concern essentially storing a history that may not be useful?  The reason I ask is because we could capture all method operation names and sore them to a log. You are right that this could get really messy and potentially meaningless as a result. 

However, what about storing the text related to the calling script used to call `to-netcdf`?  Perhaps that may work in terms of enhanced documentation.  I think there could be some utility to be gained here, especially in team environments.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,148771214