Skip to content

docs+ci: drop START.bat reference, skip build on docs-only pushes#47

Merged
OpenSource-For-Freedom merged 3 commits into
mainfrom
docs/readme-startbat
Jun 9, 2026
Merged

docs+ci: drop START.bat reference, skip build on docs-only pushes#47
OpenSource-For-Freedom merged 3 commits into
mainfrom
docs/readme-startbat

Conversation

@OpenSource-For-Freedom

@OpenSource-For-Freedom OpenSource-For-Freedom commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

Two doc-related cleanups bundled together since they share a theme: doc-only changes shouldn't masquerade as releasable code.

1. START.bat is gone from the README

PR #36 removed START.bat from the repo entirely but the README's Portable install row still told users to "click START.bat". Updated to "Double-click WRAITH.exe", which is how the actual portable flow works now.

Also relabelled the Headless quick scan section as "source build only" — quick-scan.ps1 lives in the source tree but isn't in the release ZIP, so binary-install users following those instructions hit "command not found".

2. Doc-only main pushes don't cut a release anymore

Added paths-ignore to the workflow's push trigger so commits that only touch markdown, docs/, or LICENSE don't:

  • spin up a Windows runner
  • bump the patch tag
  • publish a new release for what is by definition a no-op for users on the binary
paths-ignore:
  - '**.md'
  - 'docs/**'
  - 'LICENSE'

Unchanged: the tag-push trigger has no paths-ignore. An explicit git tag vX.Y.Z && git push origin vX.Y.Z still cuts a release regardless of which files changed — backports and explicit hotfixes are unaffected.

Things that still trigger a build: VERSION (controls patch derivation), and anything under WRAITH/, scanner/, automation/, WRAITH.Tests/, or .github/.

Test plan

  • Merge.
  • Note that this PR's own merge will NOT publish a new stable release (it's docs-only + a workflow change — the workflow change itself isn't covered by paths-ignore, so we'll get one final build for the change-that-introduces-the-skip. Subsequent doc-only commits won't.)
  • Push a one-line README edit to main → no Deploy run appears in Actions.
  • Push a VERSION bump or any code change → Deploy still runs.

START.bat was removed from the repo entirely back in PR #36 (the
release-ZIP trim) but the README's Portable column still told users
to "click START.bat". Updated to "Double-click WRAITH.exe", which is
how the actual portable flow works.

Also clarified that the Headless quick scan section (quick-scan.ps1)
applies to source builds only — quick-scan.ps1 isn't in the release
ZIP either, so binary-install users were getting "command not found"
when they tried to follow that section.
Copilot AI review requested due to automatic review settings June 9, 2026 02:04

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the README to reflect the current release ZIP contents after launcher/helper scripts were removed from the portable distribution, so users don’t follow instructions that lead to missing files.

Changes:

  • Updates the Portable install “Launcher” instruction to run WRAITH.exe directly (instead of START.bat).
  • Relabels the headless quick scan section to indicate quick-scan.ps1 is only available from a source checkout (not in the release ZIP), and adds a short note to clone the repo first.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
Comment on lines +178 to +180
### Headless quick scan (source build only)
The `quick-scan.ps1` helper ships with the source tree, not the release
ZIP. Clone the repo first, then:
Comment thread README.md
Comment on lines +178 to +180
### Headless quick scan (source build only)
The `quick-scan.ps1` helper ships with the source tree, not the release
ZIP. Clone the repo first, then:
OpenSource-For-Freedom and others added 2 commits June 8, 2026 22:28
Adds paths-ignore so commits that only touch markdown, docs/, or LICENSE
don't kick off a Windows runner, don't bump the patch tag, and don't
publish a new release for what is by definition a no-op for users on
the binary.

Tag-push trigger is unchanged — `git tag vX.Y.Z && git push origin
vX.Y.Z` still cuts a release regardless of which files changed in the
underlying commit, so backports and explicit hotfixes are unaffected.

Patterns:
  - **.md         README, CHANGELOG, CONTRIBUTING, any markdown anywhere
  - docs/**       the docs tree
  - LICENSE       license tweaks (rare) shouldn't ship a "new" version

Things that DO still trigger:
  - VERSION       (controls the patch derivation)
  - Anything in WRAITH/, scanner/, automation/, WRAITH.Tests/, .github/
Copilot AI review requested due to automatic review settings June 9, 2026 02:30
@OpenSource-For-Freedom OpenSource-For-Freedom changed the title docs(readme): drop START.bat reference, clarify headless-scan section docs+ci: drop START.bat reference, skip build on docs-only pushes Jun 9, 2026
@OpenSource-For-Freedom OpenSource-For-Freedom merged commit 7a6ae6b into main Jun 9, 2026
8 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

Comment thread README.md
Comment on lines +178 to +180
### Headless quick scan (source build only)
The `quick-scan.ps1` helper ships with the source tree, not the release
ZIP. Clone the repo first, then:
Comment on lines +35 to +37
paths-ignore:
- '**.md'
- 'docs/**'
Comment on lines +30 to +34
# Doc-only commits don't change anything that ships — skip the build,
# save the runner minutes, and keep the patch number from ticking up
# for a README typo fix. The tags trigger below is intentionally
# unrestricted: an explicit `git tag vX.Y.Z && git push` should
# always cut a release regardless of which files changed.
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.

2 participants