practicalli / practicalli/engineering-playbook
automation: the magic of cron
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Using cron
- on the OS
- in a GitHub workflow (e.g. https://github.com/vn7n24fzkq/github-profile-summary-cards)
Explaining cron patterns
- numbers represent time
- ? represents (not sure about this)
-
- represents every
References
Related
- http://www.quartz-scheduler.org/ Java job scheduler library - Apache 2.0 licence
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
Start by reviewing the cron references and the issue's two contexts: OS scheduling and GitHub workflows. Explain cron fields and patterns, clarify the uncertain '?' meaning, and include practical examples and links for both contexts; the documentation is done when these topics are understandable to a reader.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100