Skip to content

Changes to .chronus shouldn't trigger core CI #9496

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
timotheeguerin wants to merge 2 commits into from
+1 −0
Open

Changes to .chronus shouldn't trigger core CI #9496

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6b66a51
Chronus not core
timotheeguerin Jan 28, 2026
12e4f93
Merge branch 'main' into fix/chronus-not-core
iscai-msft Jan 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions eng/common/config/area.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ export const CIRules = {
"!.prettierrc.json",
"!cspell.yaml", // CSpell is already run as its dedicated CI(via github action)
"!eslint.config.json", // Eslint is already run as its dedicated CI(via github action)
"!.chronus/**/*", // Used across emitters
...ignore(isolatedEmitters),
...ignore(AreaPaths["emitter:client:csharp"]),
...ignore(AreaPaths["emitter:client:java"]),
Expand Down
Loading