From 404de393644dd09a5b2c2c457eb7dae630bf17cd Mon Sep 17 00:00:00 2001
From: Anton Larionov <11796525+anlar@users.noreply.github.com>
Date: Tue, 4 Jan 2022 04:55:03 +0400
Subject: [PATCH] Update README example with permissions block (#164)

Documentation:
- https://github.blog/changelog/2021-04-20-github-actions-control-permissions-for-github_token/
- https://docs.github.com/en/actions/security-guides/automatic-token-authentication
---
 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index 2ef7eb8..2cfcdd3 100644
--- a/README.md
+++ b/README.md
@@ -49,6 +49,8 @@ jobs:
 
   build:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
     steps:
     - uses: actions/checkout@v2
     - uses: ncipollo/release-action@v1
@@ -62,3 +64,4 @@ jobs:
 ## Notes
 - You must provide a tag either via the action input or the git ref (i.e push / create a tag). If you do not provide a tag the action will fail.
 - If the tag of the release you are creating does not yet exist, you should set both the `tag` and `commit` action inputs. `commit` can point to a commit hash or a branch name (ex - `main`).
+- In the example above only required permissions for the action specified (which is `contents: write`). If you add other actions to the same workflow you should expand `permissions` block accordingly.