From ca89da28e881311ecb058e99a0749fb5e5ef6db1 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Mon, 9 Feb 2026 12:40:55 +0700 Subject: [PATCH 01/11] docs: view updated how to request for leave --- docs/LEAVE_POLICY.md | 51 ++++++++++++++++++++++++++++++++++++++------ 1 file changed, 44 insertions(+), 7 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index b3cb7a1..14f4b1c 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -21,16 +21,53 @@ public holidays. Your personal leave year = **365 days from the date you signed your agreement**. -## How to Ask for Leave? +## How to Request Leave? -[Create Leave Request (GitHub form)](https://github.com/holdex/developers/issues/new?template=leave_request.yml). +1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) +2. **Create a new branch** for your leave request +3. **Edit the `leave.yaml` file** and add your leave dates: + - For future leave: add under `daysOff.scheduled` + - For past days: add under `daysOff.taken` -## What Happens After You Submit? + Example: + ```yaml + daysOff: + taken: + - date: 2025-12-25 + type: holiday + scheduled: + - date: 2026-01-15 + type: vacation + notes: Family trip + ``` -| Result | What HR does | -|------------|---------------------------------------------------| -| Approved | HR merges a PR and writes “Approved” in your request | -| Rejected | HR closes the request and explains why | +4. **Create a Pull Request** with your changes +5. **Wait for approval** - HR will review and merge your PR if approved +6. **After merge** - your leave is recorded and will appear in the automated summary + +### Valid Leave Types + +- `vacation` - Planned time off +- `sick` - Sick leave +- `personal` - Personal days +- `holiday` - Public/company holidays +- `unpaid` - Unpaid leave (deducted from salary) + +### Date Ranges + +You can use ranges for multi-day leave: +```yaml +- date: 2026-02-10 to 2026-02-15 + type: vacation +``` + +## Automated Leave Summary + +Every day at midnight UTC, the system automatically: +- Calculates your leave balance (days remaining/committed) +- Shows carry-over from previous year (max 3 days) +- Updates your HR issue with a detailed leave summary +- Calculates unpaid leave deductions per month ## Money Rules – Super Simple From 62b691bec3a9bac80c04cb822348071b44bd2995 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Tue, 10 Feb 2026 12:39:42 +0700 Subject: [PATCH 02/11] chore: lint --- docs/LEAVE_POLICY.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index 14f4b1c..f66cada 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -24,12 +24,13 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -2. **Create a new branch** for your leave request -3. **Edit the `leave.yaml` file** and add your leave dates: +1. **Create a new branch** for your leave request +1. **Edit the `leave.yaml` file** and add your leave dates: - For future leave: add under `daysOff.scheduled` - For past days: add under `daysOff.taken` Example: + ```yaml daysOff: taken: @@ -41,9 +42,10 @@ Your personal leave year = **365 days from the date you signed your agreement**. notes: Family trip ``` -4. **Create a Pull Request** with your changes -5. **Wait for approval** - HR will review and merge your PR if approved -6. **After merge** - your leave is recorded and will appear in the automated summary +1. **Create a Pull Request** with your changes +1. **Wait for approval** - HR will review and merge your PR if approved +1. **After merge** - your leave is recorded and will appear in the automated + summary ### Valid Leave Types @@ -56,6 +58,7 @@ Your personal leave year = **365 days from the date you signed your agreement**. ### Date Ranges You can use ranges for multi-day leave: + ```yaml - date: 2026-02-10 to 2026-02-15 type: vacation @@ -64,6 +67,7 @@ You can use ranges for multi-day leave: ## Automated Leave Summary Every day at midnight UTC, the system automatically: + - Calculates your leave balance (days remaining/committed) - Shows carry-over from previous year (max 3 days) - Updates your HR issue with a detailed leave summary From 23c7dd28fb3d01ae5dd9da2e682f0146cffb6d66 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Tue, 10 Feb 2026 22:27:08 +0700 Subject: [PATCH 03/11] chore: add more examples on multi-day leaves --- docs/LEAVE_POLICY.md | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index f66cada..a1a07a2 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -24,8 +24,8 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -1. **Create a new branch** for your leave request -1. **Edit the `leave.yaml` file** and add your leave dates: +2. **Create a new branch** for your leave request +3. **Edit the `leave.yaml` file** and add your leave dates: - For future leave: add under `daysOff.scheduled` - For past days: add under `daysOff.taken` @@ -42,9 +42,9 @@ Your personal leave year = **365 days from the date you signed your agreement**. notes: Family trip ``` -1. **Create a Pull Request** with your changes -1. **Wait for approval** - HR will review and merge your PR if approved -1. **After merge** - your leave is recorded and will appear in the automated +4. **Create a Pull Request** with your changes +5. **Wait for approval** - HR will review and merge your PR if approved +6. **After merge** - your leave is recorded and will appear in the automated summary ### Valid Leave Types @@ -64,6 +64,16 @@ You can use ranges for multi-day leave: type: vacation ``` +or for multi-day but separated, you can simply add more items on 1 PR: +```yaml +- date: 2026-02-10 + type: vacation +- date: 2026-02-12 + type: personal +- date: 2026-02-15 to 2026-02-17 + type: personal +``` + ## Automated Leave Summary Every day at midnight UTC, the system automatically: From b9aae347e7360e070521749a1c24f34d05401a31 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Tue, 10 Feb 2026 22:29:21 +0700 Subject: [PATCH 04/11] chore: lint --- docs/CONTRIBUTING.md | 14 ++++++++------ docs/LEAVE_POLICY.md | 11 ++++++----- 2 files changed, 14 insertions(+), 11 deletions(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index edacac1..e47ab63 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -116,9 +116,8 @@ See these related items: Avoid simply pasting the URL inline. ```md -Check this out: -Related: -See for details +Check this out: Related: See + for details ``` > [!NOTE] @@ -137,7 +136,8 @@ PR Requirements. For the security and integrity of our project, we require all contributors to sign their commits. For detailed instructions on why and how to sign your commits refer to -[GitHub's documentation on commit signature verification](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). +[GitHub's documentation on commit signature +verification](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). > [!Note] > We recommend signing commits using an [SSH key](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification). Ensure your Git version supports SSH signature verification (Git 2.34 or later). @@ -148,7 +148,8 @@ For detailed instructions on why and how to sign your commits refer to > Here's a [good resource](https://youtu.be/bmSAYlu0NcY?si=2lLQeY1PGCY9tcvX) on software design philosophy. When planning the scope of work, make sure you -[keep PRs small](https://artsy.github.io/blog/2021/03/09/strategies-for-small-focused-pull-requests/). +[keep PRs +small](https://artsy.github.io/blog/2021/03/09/strategies-for-small-focused-pull-requests/). You must be able to complete your PR within 3-4 hours. If the solution requires more time, then decompose it into smaller independent PRs. In case your smaller PRs can't be used on production, use feature flags. @@ -182,7 +183,8 @@ When starting to work on a Problem, you must: [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) right away. Do not mark PR as "ready to review" unless you are confident it is ready. -1. [Link opened PR](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) to the corresponding Problem (issue). +1. [Link opened PR](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) + to the corresponding Problem (issue). 1. Before marking your PR as ready for review, assign **at least one reviewer** (team or individual). Do not merge without approved review. diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index a1a07a2..f8a74c3 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -24,8 +24,8 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -2. **Create a new branch** for your leave request -3. **Edit the `leave.yaml` file** and add your leave dates: +1. **Create a new branch** for your leave request +1. **Edit the `leave.yaml` file** and add your leave dates: - For future leave: add under `daysOff.scheduled` - For past days: add under `daysOff.taken` @@ -42,9 +42,9 @@ Your personal leave year = **365 days from the date you signed your agreement**. notes: Family trip ``` -4. **Create a Pull Request** with your changes -5. **Wait for approval** - HR will review and merge your PR if approved -6. **After merge** - your leave is recorded and will appear in the automated +1. **Create a Pull Request** with your changes +1. **Wait for approval** - HR will review and merge your PR if approved +1. **After merge** - your leave is recorded and will appear in the automated summary ### Valid Leave Types @@ -65,6 +65,7 @@ You can use ranges for multi-day leave: ``` or for multi-day but separated, you can simply add more items on 1 PR: + ```yaml - date: 2026-02-10 type: vacation From 6647c18dc721b83099e4e52b4489e228cd281e26 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Tue, 10 Feb 2026 22:30:55 +0700 Subject: [PATCH 05/11] chore: revert contributing --- docs/CONTRIBUTING.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md index e47ab63..edacac1 100644 --- a/docs/CONTRIBUTING.md +++ b/docs/CONTRIBUTING.md @@ -116,8 +116,9 @@ See these related items: Avoid simply pasting the URL inline. ```md -Check this out: Related: See - for details +Check this out: +Related: +See for details ``` > [!NOTE] @@ -136,8 +137,7 @@ PR Requirements. For the security and integrity of our project, we require all contributors to sign their commits. For detailed instructions on why and how to sign your commits refer to -[GitHub's documentation on commit signature -verification](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). +[GitHub's documentation on commit signature verification](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification). > [!Note] > We recommend signing commits using an [SSH key](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification). Ensure your Git version supports SSH signature verification (Git 2.34 or later). @@ -148,8 +148,7 @@ verification](https://docs.github.com/en/authentication/managing-commit-signatur > Here's a [good resource](https://youtu.be/bmSAYlu0NcY?si=2lLQeY1PGCY9tcvX) on software design philosophy. When planning the scope of work, make sure you -[keep PRs -small](https://artsy.github.io/blog/2021/03/09/strategies-for-small-focused-pull-requests/). +[keep PRs small](https://artsy.github.io/blog/2021/03/09/strategies-for-small-focused-pull-requests/). You must be able to complete your PR within 3-4 hours. If the solution requires more time, then decompose it into smaller independent PRs. In case your smaller PRs can't be used on production, use feature flags. @@ -183,8 +182,7 @@ When starting to work on a Problem, you must: [draft PR](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) right away. Do not mark PR as "ready to review" unless you are confident it is ready. -1. [Link opened PR](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) - to the corresponding Problem (issue). +1. [Link opened PR](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) to the corresponding Problem (issue). 1. Before marking your PR as ready for review, assign **at least one reviewer** (team or individual). Do not merge without approved review. From 0d270d75d50751653c6296de4e9ec49bb7c100de Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Wed, 11 Feb 2026 00:20:20 +0700 Subject: [PATCH 06/11] docs: make steps clearer --- docs/LEAVE_POLICY.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index f8a74c3..86bfb73 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -24,7 +24,12 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -1. **Create a new branch** for your leave request +1. **Create a new issue and branch** for your leave request + + - Issue Title Example: `Leave Request: William Rusdyputra - Holiday ` + - Branch example: `leave/william-rusdyputra` + - You can define which days you are requesting on the issue description, even if the days are separated like 12th, 14th, etc. + 1. **Edit the `leave.yaml` file** and add your leave dates: - For future leave: add under `daysOff.scheduled` - For past days: add under `daysOff.taken` @@ -43,7 +48,7 @@ Your personal leave year = **365 days from the date you signed your agreement**. ``` 1. **Create a Pull Request** with your changes -1. **Wait for approval** - HR will review and merge your PR if approved +1. **Wait for approval** - HR will review it by D-1 at the latest and merge your PR if it’s approved 1. **After merge** - your leave is recorded and will appear in the automated summary From c86b595b682a452867f9c3f071ac4c962ef7a62f Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Wed, 11 Feb 2026 00:21:24 +0700 Subject: [PATCH 07/11] chore: lint --- docs/LEAVE_POLICY.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index 86bfb73..0880902 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -26,7 +26,7 @@ Your personal leave year = **365 days from the date you signed your agreement**. 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) 1. **Create a new issue and branch** for your leave request - - Issue Title Example: `Leave Request: William Rusdyputra - Holiday ` + - Issue Title Example: `Leave Request: William Rusdyputra - Holiday` - Branch example: `leave/william-rusdyputra` - You can define which days you are requesting on the issue description, even if the days are separated like 12th, 14th, etc. @@ -48,7 +48,8 @@ Your personal leave year = **365 days from the date you signed your agreement**. ``` 1. **Create a Pull Request** with your changes -1. **Wait for approval** - HR will review it by D-1 at the latest and merge your PR if it’s approved +1. **Wait for approval** - HR will review it by D-1 at the latest and merge your + PR if it’s approved 1. **After merge** - your leave is recorded and will appear in the automated summary From 19ad8c468b99ca54264bd58fab8c5506adb0b4a5 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Wed, 11 Feb 2026 00:29:30 +0700 Subject: [PATCH 08/11] chore: linter --- docs/LEAVE_POLICY.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index 0880902..47ec78c 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -28,7 +28,9 @@ Your personal leave year = **365 days from the date you signed your agreement**. - Issue Title Example: `Leave Request: William Rusdyputra - Holiday` - Branch example: `leave/william-rusdyputra` - - You can define which days you are requesting on the issue description, even if the days are separated like 12th, 14th, etc. + - You can specify the days you’re requesting in the issue description, + + even if they’re non-consecutive (e.g., the 12th and 14th). 1. **Edit the `leave.yaml` file** and add your leave dates: - For future leave: add under `daysOff.scheduled` From 51f0591235000e700cb4132c490df2ba1ebe2b29 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Wed, 11 Feb 2026 00:33:47 +0700 Subject: [PATCH 09/11] chore: linter --- docs/LEAVE_POLICY.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index 47ec78c..4a027b8 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -24,8 +24,7 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -1. **Create a new issue and branch** for your leave request - +1. **Create a new issue and branch** - Issue Title Example: `Leave Request: William Rusdyputra - Holiday` - Branch example: `leave/william-rusdyputra` - You can specify the days you’re requesting in the issue description, From 46e398878767dd3848fe43ba2b6a72c5246e4068 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Wed, 11 Feb 2026 10:32:52 +0700 Subject: [PATCH 10/11] chore: change steps --- docs/LEAVE_POLICY.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index 4a027b8..f7eef59 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -24,14 +24,11 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? 1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -1. **Create a new issue and branch** - - Issue Title Example: `Leave Request: William Rusdyputra - Holiday` - - Branch example: `leave/william-rusdyputra` - - You can specify the days you’re requesting in the issue description, +1. **Create Leave Request** on this + [Form](https://github.com/holdex/developers/issues/new?template=leave_request.yml). - even if they’re non-consecutive (e.g., the 12th and 14th). - -1. **Edit the `leave.yaml` file** and add your leave dates: +1. **Create a Pull Request** by editing the `leave.yaml` file and add your leave + dates: - For future leave: add under `daysOff.scheduled` - For past days: add under `daysOff.taken` @@ -48,7 +45,6 @@ Your personal leave year = **365 days from the date you signed your agreement**. notes: Family trip ``` -1. **Create a Pull Request** with your changes 1. **Wait for approval** - HR will review it by D-1 at the latest and merge your PR if it’s approved 1. **After merge** - your leave is recorded and will appear in the automated From 0274c4508ce567b958adb50b7dc056bd5da231a1 Mon Sep 17 00:00:00 2001 From: williamrusdyputra Date: Thu, 12 Feb 2026 10:20:43 +0700 Subject: [PATCH 11/11] docs: view how to request leave on wizard website --- docs/LEAVE_POLICY.md | 64 +------------------------------------------- 1 file changed, 1 insertion(+), 63 deletions(-) diff --git a/docs/LEAVE_POLICY.md b/docs/LEAVE_POLICY.md index f7eef59..f7c5232 100644 --- a/docs/LEAVE_POLICY.md +++ b/docs/LEAVE_POLICY.md @@ -23,69 +23,7 @@ Your personal leave year = **365 days from the date you signed your agreement**. ## How to Request Leave? -1. **Go to your HR repository** (e.g., `holdex/hr-member-yourname`) -1. **Create Leave Request** on this - [Form](https://github.com/holdex/developers/issues/new?template=leave_request.yml). - -1. **Create a Pull Request** by editing the `leave.yaml` file and add your leave - dates: - - For future leave: add under `daysOff.scheduled` - - For past days: add under `daysOff.taken` - - Example: - - ```yaml - daysOff: - taken: - - date: 2025-12-25 - type: holiday - scheduled: - - date: 2026-01-15 - type: vacation - notes: Family trip - ``` - -1. **Wait for approval** - HR will review it by D-1 at the latest and merge your - PR if it’s approved -1. **After merge** - your leave is recorded and will appear in the automated - summary - -### Valid Leave Types - -- `vacation` - Planned time off -- `sick` - Sick leave -- `personal` - Personal days -- `holiday` - Public/company holidays -- `unpaid` - Unpaid leave (deducted from salary) - -### Date Ranges - -You can use ranges for multi-day leave: - -```yaml -- date: 2026-02-10 to 2026-02-15 - type: vacation -``` - -or for multi-day but separated, you can simply add more items on 1 PR: - -```yaml -- date: 2026-02-10 - type: vacation -- date: 2026-02-12 - type: personal -- date: 2026-02-15 to 2026-02-17 - type: personal -``` - -## Automated Leave Summary - -Every day at midnight UTC, the system automatically: - -- Calculates your leave balance (days remaining/committed) -- Shows carry-over from previous year (max 3 days) -- Updates your HR issue with a detailed leave summary -- Calculates unpaid leave deductions per month +See the [Leave Request guide](https://wizard.holdex.io/docs/leave-request). ## Money Rules – Super Simple