Closed benluddy closed 4 months ago
Welcome @benluddy!
It looks like this is your first PR to kubernetes-sigs/structured-merge-diff 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes-sigs/structured-merge-diff has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
Hi @benluddy. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/approve
/assign @alexzielenski Would you be willing to be an extra pair of eyes on this one?
/ok-to-test
/approve (For real now that I've been added to OWNERS)
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: benluddy, jpbetz
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
/hold
in case you want to call convertNumber
for the *interface{}
case. I think it would be more uniform und expected. Remove hold at will.
in case you want to call
convertNumber
for the*interface{}
case. I think it would be more uniform und expected.
Updated to avoid any surprises in the future.
/lgtm
/hold cancel
If a type's implementation of json.Marshaler returns bytes representing a valid JSON object or array followed by anything other than trailing whitespace, return an error rather than ignoring the trailing data. The documentation for the Marshaler interface indicates that implementations shouldn't do this, but it is safer to check (as json.Marshal does) than to rely on it.