Feature: More sophisticated handling of forked PRs in landers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github, javascript
Research direction
Start by examining the lander configuration for examples such as spectacle/docs and trace how forked pull requests run in Travis. Compare the listed fallback options—credential-safe CI, staging deploys, PR messages, GitHub Actions, and a webhook—and define a working behavior for forked PRs before choosing an implementation.
Written by the indexing model from the issue text.
Description
Our landers (e.g. spectacle/docs) get forked PRs against the docs. But, Travis does not provide encrypted secrets for forked PRs for security reasons.
- Backstop: Should not fail CI for invalid credentials.
- Figure out if we can still do staging deploys?
- Otherwise, figure out if we can somehow do a PR message?
- CI specific feature? (Like Travis CI has special way to post comment or something)
- GitHub actions? (Note: GH token is available in forks, but it is a read-only token: https://www.edwardthomson.com/blog/github_actions_11_secrets.html)
- (UGH, ticket) a lambda webhook (like we've done before)
- Dominant language
- JavaScript
- Stars
- 7
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from FormidableLabs/formideploy
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
documentation feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
All issues in FormidableLabs/formideploy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
daisy/a11y-meta-viewer#18 ·
-
good first issue status: needs triaging type: bug version: 2.0
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
medusajs/medusa#17094 · 2 comments ·
Maintainers usually reply within 1 day
-
browser: chrome package: @carbon/react package: styles
Difficulty 1/5 Under an hour Newbie friendliness 92/100
carbon-design-system/carbon#23567 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
clerk/javascript#10033 ·
Maintainers usually reply within 1 day
-
bug client p1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel/eve#4173 · 2 comments ·
Maintainers usually reply within 1 day