Elabore/odoo-elabore-ci
9
0
Fork 0
Code Issues Pull Requests Actions Packages Releases Activity

[IMP] push directly to branches instead of creating PRs

Browse Source 
CI config changes are low-risk and don't affect business code.
Direct push eliminates the need to manually validate 50+ PRs.

Changes:
- Push commits directly to target branches (no AGit PR flow)
- Simplified commit message: '[CI] sync config from odoo-elabore-ci'
- Update README to reflect direct push behavior
This commit is contained in:
Stéphan Sainléger
2026-03-10 17:11:03 +01:00
parent 61a9e10b17
commit f86c403ab2
2 changed files with 15 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -48,7 +48,8 @@ The deployment is **manually triggered** via Gitea Actions interface, giving you
**Features:**
- **Version filter**: Deploy to all versions or a specific one (16.0, 18.0)
- **Repo filter**: Deploy to all repos or specific ones (comma-separated)
- **Dry-run mode**: Preview changes without creating any PRs
- **Dry-run mode**: Preview changes without pushing anything
- **Direct push**: Commits are pushed directly to target branches (no PR)
**Process:**
1. Detects available versions (folders in `config/` other than `common/`)
@@ -57,7 +58,7 @@ The deployment is **manually triggered** via Gitea Actions interface, giving you
- Attempts to clone the corresponding branch
- Copies `config/common/` then `config/{version}/`
- In dry-run: shows what would change
- In live mode: creates a Pull Request if changes detected
- In live mode: commits and pushes directly to the branch
### CI Workflow (`pre-commit.yml`)
@@ -93,7 +94,7 @@ Deployment is done via the Gitea Actions interface:
|-----------|-------------|----------|
| **Version** | Odoo version to deploy | `all`, `16.0`, `18.0` |
| **Repos** | Target repos (empty = all) | `crm-addons, hr-addons` |
| **Dry-run** | Preview without creating PRs | `true` (recommended first) |
| **Dry-run** | Preview without pushing | `true` (recommended first) |
#### Deployment Examples
@@ -115,7 +116,7 @@ Deployment is done via the Gitea Actions interface:
→ Review the logs to see what would change
4. If satisfied, run again WITHOUT dry-run
→ PRs are created in target repos
→ Changes are pushed directly to target branches
```
### Modifying CI Configuration