nix-config/.agent/rules/ci-cd-networking-constraints.md
Tibo De Peuter 3648b4d535
meta: add AI agent rules and skills
Create a modular, context-aware style guide for AI code assistants.

- Add nixos-architecture skill for .nix file generation and networking patterns
- Add dns-management rule to enforce Bind9 SOA serial increments
- Add cicd-networking rule for direct-IP runner authentication
- Add git-workflow rule to enforce conventional and atomic commits
2026-03-17 22:52:15 +01:00

13 lines
768 B
Markdown

---
name: cicd-networking
description: Networking constraints for CI/CD workflow files (Gitea/GitHub Actions).
globs: [".github/workflows/.yml", ".github/workflows/.yaml", ".gitea/workflows/.yml", ".gitea/workflows/.yaml"]
---
# Bos55 CI/CD Networking Constraints
When generating or modifying CI/CD workflows, strictly follow these networking practices:
1. **IP-Based Login for Reliability**
- When CI runners (like Gitea Actions) need to interact with internal services for authentication or deployment, always use direct IP addresses (e.g., `192.168.0.25`) for machine-to-machine login steps.
- **Why?** This bypasses potential DNS resolution issues or delays within the isolated runner environment, ensuring maximum robustness during automated CI/CD runs.