I am using
**GITHUB\_TOKEN** secret to make authenticated GitHub API calls on behalf of an action.
I am the maintainer of CLA Assistant OAuth App and by seeing the amazing capabilities of Github Actions, we are now developing
**CLA Lite GitHub Action**. The contributors data will be stored in the file-system (json file) inside the repository of where the
**CLAAssistant.yml** is configured.
However, we just come to know that there is only read Access but no write access when there is a Pull Request from the forked Repository, So the contributors details from the forked repository cannot be written in a file of the base repository since The permissions for the GITHUB_TOKEN in forked repositories is read-only.
It will be great If the
GITHUB_TOKEN permission can be optionally read/write and default is only read for the forked repos. And also, please suggest If there is any other work around for this use-case.