chore: update add item to project to use the unleash bot #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR updates the workflow that adds items to the project board to
use the new Unleash bot instead of my personal token.
I believe that all sub-repos are configured with the following job
definition, which should make this update automatic and smooth:
```yaml
jobs:
add-to-project:
uses: unleash/.github/.github/workflows/add-item-to-project.yml@main
secrets: inherit
```
chriswk
approved these changes
Jan 9, 2025
thomasheartman
deleted the
chore/add-unleash-bot-stuff-to-add-item-to-project
branch
thomasheartman
added a commit
that referenced
this pull request
Jan 9, 2025
This reverts commit 6518dbf.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the workflow that adds items to the project board to
use the new Unleash bot instead of my personal token.
I believe that all sub-repos (I've only checked three, but I remember copy-pasting that config file everywhere)
are configured with the following job definition, which should make this update automatic and smooth:
But interestingly, the previous secret (add to project pat) was never passed along. Maybe that's a feature you get with
secrets: inherit? Regardless, I don't think being explicit about the required secrets is a bad thing? 🤷🏼