From be12ce54ebade88842efe9dd39cea85420280ec9 Mon Sep 17 00:00:00 2001 From: mibali Date: Mon, 25 May 2026 11:03:42 +0100 Subject: [PATCH] docs: document automation policy --- docs/automations.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 docs/automations.md diff --git a/docs/automations.md b/docs/automations.md new file mode 100644 index 0000000..ae53d93 --- /dev/null +++ b/docs/automations.md @@ -0,0 +1,30 @@ +# Repository Automations + +DraftApply uses private Codex automations for repository maintenance. The full +automation prompts, schedules, runtime paths, and scheduler configuration are +intentionally not tracked in this public repository. + +The active automation policy is: + +- Automation work must happen on branches created from `main`. +- Automation changes must be proposed through draft pull requests targeting + `main`. +- Automation-created pull requests must not be merged by the automation. +- Human review is required before merge. +- Automation branches should be deleted after their pull requests are merged. +- Relevant tests should be run and reported in the pull request when code or + data changes are made. +- Secrets, local machine paths, private tokens, CV data, and raw large datasets + must not be committed. + +Current private maintenance areas include: + +- Recent-change bug scanning. +- Role-profile intelligence updates using official occupation sources. +- Salary benchmark refresh checks using official downloadable public datasets. + +For data-oriented automation work, DraftApply prefers official, standardized +sources such as O*NET, ESCO, BLS, and ONS. Scraped datasets, paid/private APIs, +and unofficial salary aggregators should not be used for repository benchmark +data. +