agentleFS
actionsactions/runner/.github/copilot-instructions.md

runner

Copilot instructions6.4k starsChanged 13 months agoMITView on GitHub

Whenever possible, changes should be accompanied by non-trivial tests that meaningfully exercise the core functionality of the new code being introduced. All tests are in the Test/ directory at the repo root. Fast unit tests are in the Test/L0 directory and by convention have the suffix L0.cs. For example: unit tests for a hypothetical src/Runner.Worker/Foo.cs would go in src/Test/L0/Worker/FooL0.cs. Run tests using this command: After editing .cs files, always format the code using this command: Wherever possible, all changes should…

We split this copilot-instructions.md into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All tests are in the Test/ directory at the repo root.

    line 7
  2. Distinctive:

    Run tests using this command:

    line 9
  3. Distinctive:

    After editing .cs files, always format the code using this command:

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Making changes

Tests

Whenever possible, changes should be accompanied by non-trivial tests that meaningfully exercise the core functionality of the new code being introduced.

All tests are in the Test/ directory at the repo root. Fast unit tests are in the Test/L0 directory and by convention have the suffix L0.cs. For example: unit tests for a hypothetical src/Runner.Worker/Foo.cs would go in src/Test/L0/Worker/FooL0.cs.

Run tests using this command:

cd src && ./dev.sh test

Formatting

After editing .cs files, always format the code using this command:

cd src && ./dev.sh format

Feature Flags

Wherever possible, all changes should be safeguarded by a feature flag; Features are declared in Constants.cs.

Download now (ZIP)

Trending

Quiet this year.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the actions/runner repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about actions/runner

The biggest 5 of 29 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 29

Talked about on Stack Overflow, Hacker News, GitHub and Bluesky (29 times).

On Stack Overflow · 15

10 more on Stack Overflow

On GitHub · 4

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.