Add write permissions to deploy docs

[clayrosenthal]

Fixing #2023, based on the repo for the action.

GitHub changed new repository default settings and made workflow permissions read-only by default. The fix was to add write permissions to the workflow:

permissions:
  contents: write

[linux-foundation-easycla]

• ✅login: clayrosenthal / (e3188dd)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @clayrosenthal!

It looks like this is your first PR to kubernetes-client/javascript 🎉. 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-client/javascript 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. 😃

[mstruebing]

/lgtm
/approve

Thanks 🚀

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: clayrosenthal, mstruebing

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mstruebing]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mstruebing]

It is still not working because of the easy CLA requirement.
I'm not sure if there is any way around this without a private access token.

[clayrosenthal]

I'm not too familiar with easy CLA, but can you change a setting to allow actions to bypass the requirement? Or make the CI bot considered having signed the CLA?

[clayrosenthal]

@mstruebing Another repo had a similar issue, it looks like you can add k8s-ci-robot to the EasyCLA allow list. Or perhaps sign in as the bot and open a dummy PR then sign the CLA