Closed levino closed 8 months ago
Latest commit: dd76900b414bd28255ac4036025207e21bbcf31d
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
jsonresume-org-homepage | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 19, 2023 10:22am |
jsonresume-org-registry | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 19, 2023 10:22am |
The changes to the repository's workflow entail removing branch restrictions for the push trigger, introducing a step to create a GitHub App token, and adjusting the usage of the GITHUB_TOKEN
environment variable to utilize the newly generated token. These modifications aim to enhance the release process automation by enabling runs on all branches and employing a more secure or specific GitHub App token for operations.
File Path | Change Summary |
---|---|
.github/workflows/release.yml |
Removed branch push trigger restrictions, added token generation step, updated GITHUB_TOKEN usage |
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?
The rabbit does not get it: When one creates PRs with the usual "github_token", no checks run in the PR. This is a design choice by github to prevent endless loops. In order to run github actions from PRs created by github actions, one has to use a "fully powered github token". One can either create a personal token, which is quite dangerous, or the proper way is to use a specific github app with limited access rights.
Summary by CodeRabbit
Chores
Refactor