Creating a Scheduler
Set up automatic backups by creating a scheduler for a repository.
Steps
- Navigate to Schedulers in the sidebar.
- Click New Scheduler to open the Create New Scheduler dialog.
- Fill in the scheduler form:
| Field | Description |
|---|---|
| Repository | Select the repository this schedule will back up. |
| Schedule Name | Optional. Leave it empty and GitSec auto-generates a name from the repository and schedule type (e.g., "Backup for org/repo (daily)"). |
| Schedule Type | Choose Daily, Weekly, Monthly, or Cron (custom CRON expression). |
| Time Zone | Choose UTC, Eastern Time (ET), or Local (Istanbul). The scheduled time is interpreted in this timezone. Shown only for Daily, Weekly, and Monthly types. |
| Included Items | Select which scopes to back up: Code & Commits, Pull Requests, Issues. At least one item must be selected. |
- Click Save to create the scheduler.
The fields shown depend on the schedule type you pick:
| Type | Fields |
|---|---|
| Daily | Time: the time of day to run the backup (24-hour format). |
| Weekly | Days of Week: select one or more days, plus Time. |
| Monthly | Day of Month: a day from 1 to 31, plus Time. |
| Cron | Cron Expression: a Quartz CRON expression (see below). No timezone selector; the expression is evaluated in UTC. |
:::info Included Items availability Wiki Pages, Projects, and Releases appear in the form but are disabled with a Coming soon badge. They cannot be selected yet. For Bitbucket repositories, the Issues option is not available. :::
Custom CRON Expressions
When you select Cron as the schedule type, you can define a fully flexible schedule using a Quartz CRON expression.
Format: second minute hour dayOfMonth month dayOfWeek
You can also enter just 5 fields (without the leading seconds field). GitSec automatically adds 0 seconds. If you enter all 6 fields, the first field must be exactly 0.
| Field | Allowed Values |
|---|---|
| second | Must be 0 (or omit the field entirely). |
| minute | 0-59 |
| hour | 0-23 |
| dayOfMonth | 1-31, *, or ? |
| month | 1-12, JAN-DEC, or * |
| dayOfWeek | 1-7 (1 = Sunday, 2 = Monday, ... 7 = Saturday), SUN-SAT, *, or ? |
dayOfMonth and dayOfWeek cannot both be *, one of them must be ?.
Examples:
| Expression | Schedule |
|---|---|
0 0 15 * * ? | Every day at 15:00 |
0 30 9 * * ? | Every day at 09:30 |
0 0 8 1 * ? | 1st of every month at 08:00 |
0 0 10 ? * 2 | Every Monday at 10:00 (2 = Monday) |
0 0 22 ? * 2-6 | Every weekday (Monday-Friday) at 22:00 |
Managing Schedulers
Saved schedulers appear in the table on the Schedulers page. For each scheduler you can:
- Toggle Active/Inactive: Use the Status switch to enable or disable the scheduler without deleting it.
- Backup Now: Trigger the scheduled backup immediately, regardless of the schedule.
- Delete: Permanently remove the scheduler. A confirmation dialog appears before deletion.
You can also view the schedulers configured for a specific repository from the Scheduler tab on its repository detail page.
:::note Excluded repositories A scheduler can be enabled only while its repository is included in the backup scope. If the repository is excluded, turning the scheduler on fails with an error explaining that the repository is not included. Re-including the repository does not turn its schedulers back on automatically, enable them manually. :::
Tips
- Set backup times during off-peak hours to avoid any potential rate limiting from your Git provider.
- Use meaningful names for schedulers so you can easily identify them (e.g., "Nightly full backup" or "Weekly code-only").
- For critical repositories, consider combining a scheduler with push event backups for maximum coverage.