Babali42/DrumBeatRepo

CI : ensure CI is triggered on open source contribution PR (forked repositories)

Closed

#532 opened on Aug 20, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (8 forks)auto 404
CIgood first issue

Repository metrics

Stars
 (23 stars)
PR merge metrics
 (Avg merge 1d 3h) (21 merged PRs in 30d)

Description

I feel like the last PRs were not triggered in CI for the tests and the linter. See the lazy loading PR to understand the situation.

Contributor guide

Research direction
Inspect the GitHub Actions workflow files in .github/workflows. Compare the 'pull request' triggers and permissions. Determine why the CI did not run on the lazy loading PR. Research how to run CI on forked PRs, using events like 'push' or 'pull request target' appropriately, and verify the fix with a test branch.
Tech stack
github actionstypescript
Domain
ci cd
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65