ci: remove PAT from release workflow#1497
Conversation
Taking inspiration from `yargs`, I've updated the workflows so that the `release` workflow no longer needs a PAT. This means CI won't automatically trigger on Release PRs anymore, but a maintainer can trigger CI by adding a `ci` label to the PR
|
👋 Hi @michaelfaith, thanks for the pull request! A scan flagged some concerns with it. Could you please take a look? [pr-task-completion] This PR's body is missing
Repositories often provide a set of tasks that pull request authors are expected to complete. Those tasks should be marked as completed with a [pr-linked-issue] This pull request is not linked as closing any issues. This repository keeps to GitHub issues for discussing potential changes. Most or all changes should be marked as approved in an issue before a pull request is sent to resolve them. To resolve this report:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1497 +/- ##
=======================================
Coverage 97.39% 97.39%
=======================================
Files 28 28
Lines 575 575
Branches 169 169
=======================================
Hits 560 560
Misses 1 1
Partials 14 14 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
PR Checklist
status: accepting prsOverview
Taking inspiration from
yargs, I've updated the workflows so that thereleaseworkflow no longer needs a PAT. This means CI won't automatically trigger on Release PRs anymore, but a maintainer can trigger CI by adding acilabel to the PR