Run deployments only on original repository
Open
bug
CI/CD
feedback
- Dominant language
- Python
- Stars
- 9
- Forks
- 31
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 16
Description
I made a fork of the repository. It tried to deploy to staging but failed because I don't have the right credentials. However, the CI shouldn't completely fail on forks, it should be skipped if possible.
Contributor guide
Research direction
Start by locating the CI deployment configuration and inspect how staging deployments are triggered for forks. Done means forked repositories skip deployment without making the CI run fail, while the original repository can still deploy to staging.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100