{"owner":"actions","repo":"runner","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":[".github/copilot-instructions.md"],"skills":{".github/copilot-instructions.md":"## Making changes\n\n### Tests\n\nWhenever possible, changes should be accompanied by non-trivial tests that meaningfully exercise the core functionality of the new code being introduced.\n\nAll 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`.\n\nRun tests using this command:\n\n```sh\ncd src && ./dev.sh test\n```\n\n### Formatting\n\nAfter editing .cs files, always format the code using this command:\n\n```sh\ncd src && ./dev.sh format\n```\n\n### Feature Flags\n\nWherever possible, all changes should be safeguarded by a feature flag; `Features` are declared in [Constants.cs](src/Runner.Common/Constants.cs).\n"},"files":{".github/copilot-instructions.md":"## Making changes\n\n### Tests\n\nWhenever possible, changes should be accompanied by non-trivial tests that meaningfully exercise the core functionality of the new code being introduced.\n\nAll 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`.\n\nRun tests using this command:\n\n```sh\ncd src && ./dev.sh test\n```\n\n### Formatting\n\nAfter editing .cs files, always format the code using this command:\n\n```sh\ncd src && ./dev.sh format\n```\n\n### Feature Flags\n\nWherever possible, all changes should be safeguarded by a feature flag; `Features` are declared in [Constants.cs](src/Runner.Common/Constants.cs).\n"},"items":[{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","title":"copilot-instructions.md","content":"## Making changes\n\n### Tests\n\nWhenever possible, changes should be accompanied by non-trivial tests that meaningfully exercise the core functionality of the new code being introduced.\n\nAll 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`.\n\nRun tests using this command:\n\n```sh\ncd src && ./dev.sh test\n```\n\n### Formatting\n\nAfter editing .cs files, always format the code using this command:\n\n```sh\ncd src && ./dev.sh format\n```\n\n### Feature Flags\n\nWherever possible, all changes should be safeguarded by a feature flag; `Features` are declared in [Constants.cs](src/Runner.Common/Constants.cs).\n","category":".github","tokens":200}]}