Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
add path to return val of file touch #55904
Here is a playbook which fails without this patch, and passes with it.
s-hertel left a comment
It seems like it would be good to document the return values instead since the path is already available in the output via
Adding an explanation of return values to the documentation would be good too.
I think that the code itself does need to change. Currently
I don't think there's any substantial drawback to modifying both. It's not even that inefficient to return both
I was a bit unclear on what to put for some of the details of the return values.
Here is a playbook which passes (with this patch). I wrote the documentation based on this behavior: