pantheon-systems / pantheon-systems/plugin-release-actions
Is it possible to avoid gh_token as an input param?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 1
- Avg merge
- 13h 6m
- Merged PRs (30d)
- 3
Description
(possibly a future investigation) Is this something that we can set and use the default built-in token if no other provided, or does the calling workflow need to set it?
Originally posted by @pwtyler in https://github.com/pantheon-systems/plugin-release-actions/pull/1#discussion_r1433122864
Contributor guide
No contributing guide indexed for this repository
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
Review the repository's GitHub Actions workflow inputs and the calling workflow configuration, then compare gh_token with GitHub's built-in token behavior. Confirm whether omitting gh_token works without caller changes and document the required configuration or update the issue with a decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100