actions/manual-approval
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Sunny 2025-06-14 02:15:56 +05:30 • committed by GitHub
parent e61c573156
commit b78b201d57
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -99,6 +99,12 @@ steps:
GitHub has a rich library of emojis, and these all work in additional approved words or denied words. Some values GitHub will store in their text version - i.e. `:shipit:`. Other emojis, GitHub will store in their unicode emoji form, like ✅.
For a seamless experience, it is recommended that you add the custom words to a GitHub comment, and then copy it back out of the comment into your actions configuration yaml.
# v1.9.x → v1.10.0
🚨 Update: Approval Issue Content Handling 🚨
Starting from v1.10.0, the behaviour for issue contents has changed:
- The issue-body and issue-body-file-path are now added as comments on the issue instead of being set as the issue’s main description/body.
- The issue title is now exactly what is provided as input, instead of being appended to or wrapped in a predefined string.
## Org team approver
If you want to have `approvers` set to an org team, then you need to take a different approach. The default [GitHub Actions automatic token](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token) does not have the necessary permissions to list out team members. If you would like to use this then you need to generate a token from a GitHub App with the correct set of permissions.