tdpeuter/bos55-nix-config-cicd
1
Fork 0
forked from Bos55/nix-config
Code Pull requests 1 Releases Packages Activity Actions
bos55-nix-config-cicd/.agent/rules/ci-cd-networking-constraints.md
Tibo De Peuter 3648b4d535
Some checks failed
Build / build (Testing) (pull_request) Has been cancelled
Details
Build / build (Development) (pull_request) Has been cancelled
Details
Build / Determining hosts to build (pull_request) Failing after 10m10s
Details
Build / Determining hosts to build (push) Failing after 11m10s
Details
Build / build (Testing) (push) Failing after 13m36s
Details
Build / build (Development) (push) Failing after 15m18s
Details
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

768 B
Raw Permalink Blame History

name description globs
cicd-networking Networking constraints for CI/CD workflow files (Gitea/GitHub Actions).
.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.