Skip to content

chore: remove AppVeyor-era orphan code#22

Merged
ChrisonSimtian merged 2 commits into
mainfrom
chore/remove-appveyor-orphans
May 18, 2026
Merged

chore: remove AppVeyor-era orphan code#22
ChrisonSimtian merged 2 commits into
mainfrom
chore/remove-appveyor-orphans

Conversation

@ChrisonSimtian

@ChrisonSimtian ChrisonSimtian commented May 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

These five files were dead the moment AppVeyor came out of the pipeline — they just compiled clean, so nobody noticed. Sweeping them out so `Build.cs` reflects what we actually run.

Files removed

File Why dead
`build/Build.Announce.cs` All four targets (Slack/Discord/Twitter/Mastodon) `.Requires(secret)` on values only AppVeyor was wired to inject.
`build/Build.SignPackages.cs` `ISignPackages` in `Nuke.Components` hardcodes `.OnlyWhenStatic(() => AppVeyor != null)` — target permanently skips without AppVeyor.
`build/Build.ReleaseImage.cs` Generated the release-announcement PNG consumed only by `Announce`.
`build/AwtrixNotificationsAttribute.cs` MQTT-driven LED-display notifier for the previous maintainer's personal IoT setup ("Awtrix"). Not applied anywhere in this codebase.
`build/Build.CustomNaming.cs` Emoji-prefix dictionary referenced only by the deleted TeamCity/AzurePipelines configuration subclasses.

Build.cs

  • Drop `IHazTwitterCredentials` from the partial-class inheritance list.
  • Drop the matching `TwitterCredentials` property.

Package drops (`build/_build.csproj`)

Used only by the removed files:

  • `linqtotwitter`
  • `MQTTnet`
  • `SixLabors.ImageSharp.Drawing`

Test plan

  • `dotnet build build/_build.csproj` — 0 errors, 0 warnings (was 9)
  • CI ubuntu-latest green

🤖 Generated with Claude Code

These files were dead the moment AppVeyor came out of the pipeline,
just nobody noticed because they compiled clean. Sweeping them out so
Build.cs is honest about what we actually run.

Files removed:
- build/Build.Announce.cs — Twitter/Slack/Discord/Mastodon announcement
  targets. All four had .Requires(secret) on values that only AppVeyor
  was wired to inject. Dead in trunk.
- build/Build.SignPackages.cs — ISignPackages base hardcodes
  .OnlyWhenStatic(() => AppVeyor != null) in Nuke.Components, so the
  target permanently skips. Our override was a no-op.
- build/Build.ReleaseImage.cs — generated a release-announcement PNG
  consumed only by Announce. Orphan once Announce is gone.
- build/AwtrixNotificationsAttribute.cs — MQTT-driven LED-display
  notifier for an "Awtrix" IoT device (personal hardware setup of the
  previous maintainer). Not applied anywhere in this codebase.
- build/Build.CustomNaming.cs — emoji-prefix dictionary used only by
  the deleted TeamCity/AzurePipelines configuration subclasses.

Build.cs changes:
- Drop `IHazTwitterCredentials` from the partial-class inheritance
  list and the matching `TwitterCredentials` property.

build/_build.csproj package drops (used only by the removed files):
- linqtotwitter
- MQTTnet
- SixLabors.ImageSharp.Drawing

Build verified clean (0 errors, 0 warnings).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Every PR was firing ubuntu-latest twice — once for the push event,
once for the pull_request event — because GitHub fires both for
same-repo branch pushes with an open PR. Doubling CI runtime and
credits for no extra signal.

Keeping pull_request only:
- Fork PRs continue to trigger (pull_request fires from forks; push
  doesn't go to the parent repo).
- paths-ignore semantics work naturally on pull_request (they were
  already a no-op for the push trigger).
- Pushes to a feature branch without an open PR no longer trigger CI.
  In trunk-based that's fine — the PR is the work unit.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian merged commit 3be8c67 into main May 18, 2026
1 check passed
@ChrisonSimtian
ChrisonSimtian deleted the chore/remove-appveyor-orphans branch May 18, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant