[02:03] PR operator#505 closed: Pebble files API client functions [03:18] Issue operator#512 opened: Tune recently added file API function naming and calling convention [04:11] Issue operator#512 closed: Tune recently added file API function naming and calling convention [04:11] Issue operator#407 opened: Have a quick "what you should look for" as packaging docs [04:11] PR operator#505 opened: Pebble files API client functions [04:11] PR operator#511 opened: Added a much more explanatory docstring to the module [04:12] Issue operator#407 closed: Have a quick "what you should look for" as packaging docs [04:12] Issue operator#512 opened: Tune recently added file API function naming and calling convention [04:12] PR operator#505 closed: Pebble files API client functions [04:12] PR operator#511 closed: Added a much more explanatory docstring to the module [05:20] PR operator#513 opened: Rename read_content/write_content to pull/push; use file-like objects [05:35] Issue operator#512 closed: Tune recently added file API function naming and calling convention [05:35] Issue operator#407 opened: Have a quick "what you should look for" as packaging docs [05:35] PR operator#513 closed: Rename read_content/write_content to pull/push; use file-like objects [05:35] PR operator#505 opened: Pebble files API client functions [05:35] PR operator#511 opened: Added a much more explanatory docstring to the module [05:36] Issue operator#407 closed: Have a quick "what you should look for" as packaging docs [05:36] Issue operator#512 opened: Tune recently added file API function naming and calling convention [05:36] PR operator#505 closed: Pebble files API client functions [05:36] PR operator#511 closed: Added a much more explanatory docstring to the module [05:36] PR operator#513 opened: Rename read_content/write_content to pull/push; use file-like objects [05:41] Issue operator#512 closed: Tune recently added file API function naming and calling convention [05:41] Issue operator#407 opened: Have a quick "what you should look for" as packaging docs [05:41] PR operator#505 opened: Pebble files API client functions [05:41] PR operator#511 opened: Added a much more explanatory docstring to the module [05:42] Issue operator#407 closed: Have a quick "what you should look for" as packaging docs [05:42] Issue operator#512 opened: Tune recently added file API function naming and calling convention [05:42] PR operator#505 closed: Pebble files API client functions [05:42] PR operator#511 closed: Added a much more explanatory docstring to the module [05:42] PR operator#513 opened: Rename read_content/write_content to pull/push; use file-like objects [05:50] Issue operator#512 closed: Tune recently added file API function naming and calling convention [05:50] Issue operator#407 opened: Have a quick "what you should look for" as packaging docs [05:50] PR operator#513 closed: Rename read_content/write_content to pull/push; use file-like objects [05:50] PR operator#505 opened: Pebble files API client functions [05:50] PR operator#511 opened: Added a much more explanatory docstring to the module [05:51] Issue operator#407 closed: Have a quick "what you should look for" as packaging docs [05:51] Issue operator#512 opened: Tune recently added file API function naming and calling convention [05:51] PR operator#505 closed: Pebble files API client functions [05:51] PR operator#511 closed: Added a much more explanatory docstring to the module [05:51] PR operator#513 opened: Rename read_content/write_content to pull/push; use file-like objects [12:36] Issue operator#512 closed: Tune recently added file API function naming and calling convention [12:36] PR operator#513 closed: Rename read_content/write_content to pull/push; use file-like objects [19:32] Issue operator#514 opened: Pebble.add_layer has a poor exception type [23:01] PR operator#515 opened: Pebble testing