temporalio / temporalio/documentation
Update Schedules docs with common issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 173
- Forks
- 330
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 156
Description
Looking to add a section in Schedules documentation to cover the common pitfalls when users configure their specs.
This thread has all the information needed https://temporaltechnologies.slack.com/archives/C0355AFA7PY/p1786645610313519|https://temporaltechnologies.slack.com/archives/C0355AFA7PY/p1786645610313519
Also, here is the internal documentation, showing examples : https://app.notion.com/p/temporalio/WIP-Scheduler-Runs-Documentation-3b88fc56773880db80c9fcfaa23a7911?source=copy_link|app.notion.com/p/temporalio/WIP-Schedule…?source=copy_link. Let me know what is the best process here, if I should send the PR or work with a docs eng to update it.
Contributor guide
No contributing guide indexed for this repository
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
Start with the Schedules documentation and review the linked Slack thread and internal Notion documentation for the common configuration pitfalls and examples. Done means the Schedules docs contain a clear section covering those issues and examples, with the appropriate documentation update prepared for review.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100