Skip to content

fix: support specifiers in ExecStart= (Resolves #529) - #530

Merged
SJrX merged 2 commits into
242.xfrom
issue-529
Sep 4, 2026
Merged

fix: support specifiers in ExecStart= (Resolves #529)#530
SJrX merged 2 commits into
242.xfrom
issue-529

Conversation

@SJrX

@SJrX SJrX commented Sep 4, 2026

Copy link
Copy Markdown
Owner

No description provided.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

Unit Test Results (grammar engine false)

1 309 tests   1 309 ✅  1m 0s ⏱️
  333 suites      0 💤
  333 files        0 ❌

Results for commit 709e7de.

♻️ This comment has been updated with latest results.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

Unit Test Results (grammar engine true)

1 309 tests   1 309 ✅  58s ⏱️
  333 suites      0 💤
  333 files        0 ❌

Results for commit 709e7de.

♻️ This comment has been updated with latest results.

Add two tests exercising every specifier in
ExecOptionValue.ABSOLUTE_PATH_SPECIFIERS: one asserting no warning for all
14 absolute-path specifiers (h s C d D E L S t T V y Y f), and one asserting
the "use an absolute path" recommendation still fires for non-absolute
text specifiers. Closes the coverage gap where a typo in the whitelist
could silently regress most specifiers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@SJrX
SJrX merged commit 86da4ff into 242.x Sep 4, 2026
5 checks passed
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