Skip to main content

rule official · GitHub

fedora-linux — GitHub Copilot rule: what it does, how to install

Sets Fedora administration standards for GitHub Copilot, focusing on dnf workflows, systemd drop-ins, and strict SELinux enforcement.

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓

.github/instructions/fedora-linux.instructions.md

What fedora-linux does

The rule instructs GitHub Copilot to generate commands and administration guides tailored to Fedora releases. It mandates modern tools, prioritizing dnf and firewall-cmd. Package operations rely on dnf history for rollback support and rpm -qi for package inspection. Any mention of COPR repositories requires explicit support warnings.

Service configuration relies on drop-in files placed in /etc/systemd/system/<unit>.d/ rather than modified unit files. Network rules default to firewalld. Unless requested otherwise, Copilot keeps SELinux in enforcing mode. To fix access denials, it applies targeted adjustments with semanage, setsebool, and restorecon instead of broad audit2allow rules. Risky changes must provide explicit rollback steps.

What it helps with

configure systemd services using drop-in files
resolve SELinux access denials with targeted semanage rules
revert package changes using dnf history rollback
manage host firewalls with firewalld commands

Example prompts for the agent

Create a systemd drop-in override for a custom service in Fedora
Show the dnf history command to revert the previous package transaction
Fix a permission denial for an Nginx socket using semanage and restorecon

How to install fedora-linux

Manually: put the files in place

.github/instructions/fedora-linux.instructions.md

The applyTo field sets which files it applies to

Manually: put the files in place

.claude/rules/fedora-linux.md

The paths frontmatter field limits the files: move applyTo from the source into paths

Manually: put the files in place

.cursor/rules/fedora-linux.mdc

Frontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own

Manually: put the files in place

.devin/rules/fedora-linux.md

Manually: put the files in place

.clinerules/fedora-linux.md

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about fedora-linux

How to install fedora-linux in GitHub Copilot?

Create the file .github/instructions/fedora-linux.instructions.md in your repository and save the rule content there.

What does the fedora-linux rule do?

It guides GitHub Copilot to follow Fedora practices, covering dnf package management, systemd drop-in directories, and enforcing SELinux policies.

How does it handle SELinux configuration?

It keeps SELinux in enforcing mode by default, directing the assistant to use semanage, setsebool, and restorecon instead of generating broad audit2allow rules.

Source text

fedora-linux.instructions.md · MIT

---
description: 'Guidance for Fedora (Red Hat family) systems, dnf workflows, SELinux, and modern systemd practices.'
applyTo: '**'
---

# Fedora Administration Guidelines

Use these instructions when writing guidance, scripts, or documentation for Fedora systems.

## Platform Alignment

- State the Fedora release number when relevant.
- Prefer modern tooling (`dnf`, `systemctl`, `firewall-cmd`).
- Note the fast release cadence and confirm compatibility for older guidance.

## Package Management

- Use `dnf` for installs and updates, and `dnf history` for rollback.
- Inspect packages with `dnf info` and `rpm -qi`.
- Mention COPR repositories only with clear support caveats.

## Configuration & Services

- Use systemd drop-ins in `/etc/systemd/system/<unit>.d/`.
- Use `journalctl` for logs and `systemctl status` for service health.
- Prefer `firewalld` unless using `nftables` explicitly.

## Security

- Keep SELinux enforcing unless the user requests permissive mode.
- Use `semanage`, `setsebool`, and `restorecon` for policy changes.
- Recommend targeted fixes instead of broad `audit2allow` rules.

## Deliverables

- Provide commands in copy-paste-ready blocks.
- Include verification steps after changes.
- Offer rollback steps for risky operations.

© github · MIT · github/awesome-copilot

Similar IDE rules

All IDE rules for DevOps and infrastructure →

From the same set770

The whole set →

github-actions-ci-cd-best-practices A GitHub Copilot rule that guides workflow structure, token permissions, caching and matrix setups whenever you touch files under .github/workflows/. ★ 40,418repo stars gilfoyle-code-review Turns GitHub Copilot into the sardonic systems architect from Silicon Valley. It delivers ruthless code critiques on architecture, speed, and security flaws without sugar-coating. ★ 40,418repo stars generate-modern-terraform-code-for-azure This rule guides GitHub Copilot when it works on Azure Terraform files, from provider selection to validation. Use it to shape infrastructure code in .tf files. ★ 40,418repo stars genaiscript A GitHub Copilot rule that turns the assistant into a GenAIScript expert: it writes scripts and answers questions about the language. ★ 40,418repo stars exclude-prompt-data This rule keeps prompt instructions and commentary out of edited files. Use it when Copilot generates code or documentation from a request. ★ 40,418repo stars draw-io Tells Copilot how to build and edit draw.io diagrams: mxGraph XML structure, a semantic colour palette, grid alignment and a validation script. ★ 40,418repo stars dotnet-wpf Directs GitHub Copilot to write WPF desktop code using the MVVM pattern on .NET 8.0+. It prevents business logic leaks into code-behind files. ★ 40,418repo stars dotnet-upgrade A GitHub Copilot rule for staged .NET upgrades, covering project dependencies, builds, tests, and CI/CD checks. ★ 40,418repo stars

Project sponsors

Companies that keep this analytics open

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor