Handle forks and secrets politely
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 199
- Forks
- 67
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 3
Description
The current behavior of this plugin is very hostile to forks.
This is what I was trying to add to a workflow so that it wouldn't waste slots and resources on my forks:
https://github.com/jsoref/zio-http/commit/0309bf26820d0600896d6f9105ae969802e9f7ba
It doesn't work because this plugin also screams if the workflow is out of sync. So, please kindly add something functionally equivalent to the above commit so that when users do work (both pushes and pull requests) in forks and they don't have the secrets that the root of the fork network has, the workflow won't hang for hours before dying.
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 reviewing the linked commit and locating the plugin's workflow synchronization and secret-handling entry points; no files or tests are named in the issue. Done means fork pushes and pull requests without the upstream secrets avoid hanging for hours, while workflows that are out of sync are handled without blocking those fork runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, scala
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100