Bug: Detect read-only token for deployment API.

Open
#39 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
api, devops

Research direction

Read lib/github/deployment.js first and trace how token presence currently selects deployment API calls. Investigate how the GitHub Actions token’s read-only status can be identified, then verify that deployment actions are skipped for it while writable tokens still attempt deployment; no test file is named in the issue.

Written by the indexing model from the issue text.

Description

bug

Our lib/github/deployment.js just checks the presence of a token to decide if it should attempt the deployment API. But in GH actions, there is a token, just a read-only one, so it actually fails.

Tasks:

  • Detect read-only token and skip deployment actions
Dominant language
JavaScript
Stars
7
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FormidableLabs/formideploy

All issues in FormidableLabs/formideploy

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.