## Description
The GITHUB_TOKEN is used in the `gh release upload` command to
upload a new basetools release. This adds content write permission
to allow the upload to work when the default permission is read-only
for the token.
(cherry picked from commit 1cab22a70e)
- [ ] Impacts functionality?
- **Functionality** - Does the change ultimately impact how firmware
functions?
- Examples: Add a new library, publish a new PPI, update an algorithm,
...
- [ ] Impacts security?
- **Security** - Does the change have a direct security impact on an
application,
flow, or firmware?
- Examples: Crypto algorithm change, buffer overflow fix, parameter
validation improvement, ...
- [ ] Breaking change?
- **Breaking change** - Will anyone consuming this change experience a
break
in build or boot behavior?
- Examples: Add a new library class, move a module to a different repo,
call
a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
- **Tests** - Does the change include any explicit test code?
- Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
- **Documentation** - Does the change contain explicit documentation
additions
outside direct code modifications (and comments)?
- Examples: Update readme file, add feature readme file, link to
documentation
on an a separate Web page, ...
## How This Was Tested
- Verified failure with read-only token on fork. Confirmed success with
the change.
## Integration Instructions
N/A - Only affects local repro GitHub workflow.
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
a4121d4aec