Create new github-bot personal token for nodejs/tweet automation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
This week, @joesepi and I spent some time on automating the nodejs/tweet repo so we can consistently and easily get out any tweets that should be going out regularly. We started with two, and in the process came across a tiny hitch: for one action to trigger another, we need to use a PAT instead of the Actions-provided token since one action can't trigger off of another if there's a GitHub provided token being used in the other.
Per @gr2m's advice (he is the maintainer of both Actions we're consuming), we need a PAT from the bot with the following permission:
- repo_public
References:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading this issue and the referenced reviews and comments in nodejs/tweet pull requests 10 and 13. Confirm the bot identity, the requested repo_public permission, and the secure handoff process; done means the automation has the required credential without exposing its value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- authentication, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100