Skip to content

Finish the pull_request paths-ignore sweep on the 16 remaining repos #5

Description

@matt-edmondson

Context

Every dotnet.yml skipped CI for pull requests touching only .md files:

pull_request:
  paths-ignore: ["**.md", ".github/ISSUE_TEMPLATE/**", ".github/pull_request_template.md"]

That makes any ruleset requiring Build, Test & Release block such PRs permanently, because the check never reports. It also affects PRs editing DESCRIPTION.md and TAGS.md, which the Terraform workspace derives repository metadata from.

The filter has been removed from the pull_request trigger in 41 repos. The push trigger keeps its own paths-ignore, deliberately, because release gating runs off KtsuBuild's should_release rather than the event type, so a docs-only push to main could otherwise cut a release.

Verified on the pilot: a PR touching README.md now runs Build, Test & Release, where previously it ran nothing.

Remaining

Seven repos are on active feature branches. Sweeping them would commit onto in-progress work:

AppDataStorage, Essentials, GitIntegration, KtsuBuild, PkmnDB, plus the BlastMerge-essentials-di and ImGuiApp-imagegui-support clones.

Nine repos on main carry unpushed commits. The sweep ends in git push, which pushes the whole branch, so it would publish unrelated work:

Abstractions, Common, Ecosystem, FileSystemProvider, ImGuiApp, IntervalAction, PersistenceProvider, SerializationProvider, UniversalSerializer

Two are archived and read-only, so they are out of scope permanently: CrossRepoActions, SyncFileContents.

Acceptance criteria

  • Local work in the affected repos is pushed or set aside
  • The sweep is completed for the 16 non-archived repos
  • Each file retains exactly one paths-ignore, under push

Method

scripts/Remove-PathsIgnore.ps1 in the infrastructure repo does the edit. Commit with [skip ci] in the subject unless a release is wanted, because KtsuBuild cuts a version on any untagged commit to main. VersionType.Skip fires only when there are no commits in range or all commits carry that tag.

Do not rebase. icon.png is stored in Git LFS across this org and rebases fail on the smudge filter. Fetch and reset to origin/main, re-apply, and push.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions