cross-repo-test runs inline in the NotificationMonitor
Open
Nobody has claimed this yet.
bug
stale
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
cross-repo-test runs inline in the NotificationMonitor. This means it has to process the entire thing before moving on to the next notification. The NotificationMonitor was designed around more lightweight tasks like adding a label, so cross-repo-test should probably be done as a dedicated sidekiq worker.
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
Locate the NotificationMonitor and the code path that runs cross-repo-test inline. Read how notifications are processed and how Sidekiq workers are defined in the repository before deciding the worker boundary. Done means cross-repo-test runs in a dedicated worker and the monitor can move on to subsequent notifications independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100