data batch docstring re-formatting: 'Examples:' -> 'Examples'#362
Merged
sadielbartholomew merged 1 commit intoMar 22, 2022
Conversation
Collaborator
|
Great. Can we just merge this now and I'll check for conflicts in the PRs that are currently up? |
Member
Author
Sure, whatever you prefer - I just didn't want to create merge difficulties for you, though |
This was referenced Mar 22, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As for #182 over on cfdm, but note that this is only across the data module, i.e:
in line with our approach to managing development of mostly
datamodules onlama-to-daskand all other modules onmaster. I am about to open a corresponding PR onmasterto cover all non-datamodules.@davidhassell I have opened this PR so the batch update gets done at the first available point, but please prioritise merging of your currently-open PRs before this - it is trivial to manage code updates and to resolve merge conflicts here, much less so (probably) on your PRs.