Scheduled workflows
The project uses multiple GitHub Actions workflows to automate different stages of the pipeline. Typical responsibilities include:- Discovering new opportunities
- Updating the
careers-datarepository - Publishing new opportunities to Discord
- Processing manually queued opportunities
Required repository secrets
Several workflows require repository secrets to authenticate with external services.
Additional secrets may be introduced as new workflows or integrations are added.
Workflow execution
Most workflows support two execution modes.Scheduled execution
Runs automatically according to the configured cron schedule. Suitable for production deployments.Manual execution
Can be triggered from the GitHub Actions interface using Run workflow. Useful when testing new sources or verifying recent changes.Monitoring workflow runs
Every workflow execution is recorded under the repository’s Actions tab. For each run you can inspect:- Workflow logs
- Step execution
- Generated artifacts
- Failure messages
- Execution duration
Common issues
The most common workflow failures are caused by:- Missing repository secrets
- Invalid Discord credentials
- Insufficient repository permissions
- Authentication failures when accessing
careers-data - Temporary network failures while collecting jobs

