Holidays and business days
Set on the Rules step.
The calendar
- Country (and optional Region): public holidays for that place, built into the app. No network call is made. “None” means weekends only.
- Extra holidays: days that are not business days for you (a company closing day).
- Removed holidays: days of the country calendar that you work anyway.
- Weekend days follow the country: Saturday and Sunday by default; Friday and Saturday in Algeria, Bahrain, Bangladesh, Egypt, Israel, Libya, Saudi Arabia and Sudan, and in the Malaysian states of Kedah, Kelantan and Terengganu; Friday in Iran; Friday and Sunday in Brunei. The Rules step shows the weekend of the country and region you pick. With no country, the weekend is Saturday and Sunday. In Quick Start, Every weekday follows the same working week (Sunday to Thursday in Saudi Arabia), and the weekend moves name the days of that country (“Move to the Thursday before”).
- Only public holidays count. Bank-only, optional, school and observance days do not, and neither does a holiday that starts after midnight (half days). Add any other day yourself as an extra holiday.
- A removed day that falls on a weekend day is still a weekend day. A date cannot be both extra and removed.
- The administrator can set a default country for new schedules.
- The country picker shows 207 places from the bundled
date-holidaysdata. See the country list. Region choices appear when that country has them.
The policy
What happens when a date falls on a weekend or holiday: | Policy | Result | |—|—| | Create anyway | The issue is created on that date. | | Move to previous business day | Moves back to the closest business day. | | Move to next business day | Moves forward to the closest business day. | | Skip | No issue for that date. |
The policy applies to the due date. Early creation is not moved (see Early creation).
Behaviours to know
- Never leaves the month (or year). For monthly rules a move stays in the calendar month; for yearly rules, in the calendar year. If “next business day” would cross into the next month, RepeatWise uses the previous business day instead (and the other way round). Example: last day of July 2027 is a Saturday, next business day would be 2 August, so the issue is due Friday 30 July. The Review step says “Moved to the nearest business day in the other direction to stay in the month”.
- Daily, weekly: no limit. A move may cross a month boundary.
- Several dates, one day. If a Saturday, Sunday and Monday date all move to Monday, only one issue is created at that time. The others are merged (shown in the log as “Merged into an earlier occurrence”).
- “Business days only” (daily). Counts every N-th business day. Weekends and holidays are not dates at all: nothing is skipped or logged.
- Business-day positions. “Last business day” and “1st business day” already land on a business day; the policy has no effect on them.
- Skipped dates count. With “After N occurrences”, a date skipped by the policy still uses one of the N.
- A schedule with a policy of Skip still previews 10 issues: skipped dates are not counted against the 10.
- No business day at all in the period (only possible with manual holidays): the date is left unchanged.
Examples (France, 08:00)
- Last day of February 2027 is a Sunday. “Last business day” gives Friday 26 February. “Last day of the month” with previous business day gives the same.
- 1 May 2027 is a Saturday and a holiday. “1st business day” gives Monday 3 May.
- Whit Monday 17 May 2027 with next business day gives Tuesday 18 May.
Third-party data
Public holiday data comes from date-holidays, which draws on Wikipedia and other community sources listed in its LICENSE. The package’s LICENSE says the holiday data is CC BY-SA 3.0 and its code is ISC. Its package.json declares (ISC AND CC-BY-3.0).
Public holiday data comes from the open-source date-holidays package by commenthol, based on Wikipedia articles, and is used unmodified under the Creative Commons Attribution-ShareAlike 3.0 licence (CC BY-SA 3.0). The package code is under the ISC licence.