Why do you want to contribute?
Hi Trigger.dev team! 👋
I'd like to request a vouch so I can start contributing to the project.
I'm a recent Computer Science graduate who has been focusing on improving my ability to work with production-scale TypeScript codebases through open source. Rather than jumping straight into coding, I've been spending time understanding architecture, execution flow, and debugging unfamiliar systems.
For Trigger.dev, I've been studying the codebase before making any changes. So far I've traced the execution flow for issue #2494 ("Make the default run list filters more explicit") from the API route through the presenters and into the shared time filtering logic to understand where the behavior is actually implemented. My goal is to implement one of the proposed solutions while following the existing architecture and keeping the change focused.
I'm hoping to become a long-term contributor, not just submit a single PR. My goal is to continue learning from the codebase while making thoughtful, production-quality contributions.
Prior contributions or relevant experience
Recently, I made my first production open source contribution to the Agent Orchestrator project, where I worked on a GitHub Actions release workflow issue. Through that contribution I learned a lot about production workflows, code review, rebasing, CI, and keeping pull requests focused.
Why do you want to contribute?
Hi Trigger.dev team! 👋
I'd like to request a vouch so I can start contributing to the project.
I'm a recent Computer Science graduate who has been focusing on improving my ability to work with production-scale TypeScript codebases through open source. Rather than jumping straight into coding, I've been spending time understanding architecture, execution flow, and debugging unfamiliar systems.
For Trigger.dev, I've been studying the codebase before making any changes. So far I've traced the execution flow for issue #2494 ("Make the default run list filters more explicit") from the API route through the presenters and into the shared time filtering logic to understand where the behavior is actually implemented. My goal is to implement one of the proposed solutions while following the existing architecture and keeping the change focused.
I'm hoping to become a long-term contributor, not just submit a single PR. My goal is to continue learning from the codebase while making thoughtful, production-quality contributions.
Prior contributions or relevant experience
Recently, I made my first production open source contribution to the Agent Orchestrator project, where I worked on a GitHub Actions release workflow issue. Through that contribution I learned a lot about production workflows, code review, rebasing, CI, and keeping pull requests focused.