You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a full-stack TypeScript engineer (Next.js / React / Node) and I work on background-job and queueing code day to day, which is what drew me to Trigger.dev. I'd like to start with small, self-contained, verifiable fixes rather than anything sweeping:
docs: dev --env-file help/docs say it does not reach tasks, but it does #4425 — the --env-file help text and the cli-dev-commands / cli-deploy-commands / cli-preview-archive docs all say the file "will only hydrate the process.env of the CLI process, not the tasks", but in dev the file is passed through to the run environment. The docs and the behaviour disagree, so one of the two should move; happy to fix the wording, or the behaviour, whichever the team considers correct.
3 code samples in your docs no longer compile #4782 — three docs samples (PromptHandle, PromptIdentifier, PromptVariables on the Prompts page) reference exports that no longer exist in @trigger.dev/sdk, so they no longer type-check.
Both are low-risk and easy to verify, which seemed like the right way to start.
For transparency: I opened #4035 back in June (docs typo fixes) before I understood how vouching worked here, and it was auto-closed. I'd rather ask first this time than have another PR closed by the bot.
Prior contributions or relevant experience
Merged open-source work, all small focused fixes of the same kind:
Why do you want to contribute?
I'm a full-stack TypeScript engineer (Next.js / React / Node) and I work on background-job and queueing code day to day, which is what drew me to Trigger.dev. I'd like to start with small, self-contained, verifiable fixes rather than anything sweeping:
dev --env-filehelp/docs say it does not reach tasks, but it does #4425 — the--env-filehelp text and thecli-dev-commands/cli-deploy-commands/cli-preview-archivedocs all say the file "will only hydrate theprocess.envof the CLI process, not the tasks", but indevthe file is passed through to the run environment. The docs and the behaviour disagree, so one of the two should move; happy to fix the wording, or the behaviour, whichever the team considers correct.PromptHandle,PromptIdentifier,PromptVariableson the Prompts page) reference exports that no longer exist in@trigger.dev/sdk, so they no longer type-check.Both are low-risk and easy to verify, which seemed like the right way to start.
For transparency: I opened #4035 back in June (docs typo fixes) before I understood how vouching worked here, and it was auto-closed. I'd rather ask first this time than have another PR closed by the bot.
Prior contributions or relevant experience
Merged open-source work, all small focused fixes of the same kind:
PRODUCT_CATEGORY_DELETEDon soft delete), fix(loyalty-plugin): respect user locale in currency formatting medusajs/medusa#15725 (respect user locale in currency formatting), fix(eslint-plugin): remove use-query-context-utility rule medusajs/medusa#15850 (remove a dead eslint rule), docs: fix typos across learn guides medusajs/medusa#15795 (docs)cron_inputto the Python SDK's workflow/task declarations), docs: fix typos in events, sticky-assignment, and prometheus-metrics pages hatchet-dev/hatchet#4194 (docs)GitHub profile: https://github.com/adem-loghmari