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
768 B
768 B
| name | description | globs | ||||
|---|---|---|---|---|---|---|
| cicd-networking | Networking constraints for CI/CD workflow files (Gitea/GitHub Actions). |
|
Bos55 CI/CD Networking Constraints
When generating or modifying CI/CD workflows, strictly follow these networking practices:
- 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.
- When CI runners (like Gitea Actions) need to interact with internal services for authentication or deployment, always use direct IP addresses (e.g.,