Skip to content

Document phony and always targets#4

Merged
leynos merged 3 commits intomainfrom
codex/extend-target-design-with-phony-and-always-flags
Jul 12, 2025
Merged

Document phony and always targets#4
leynos merged 3 commits intomainfrom
codex/extend-target-design-with-phony-and-always-flags

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 12, 2025

Summary

  • describe optional actions block
  • document phony and always flags in manifests
  • reflect new behaviour in IR generation and Ninja synthesis
  • update roadmap with a task for these flags

Testing

  • make fmt
  • make lint
  • make test
  • make markdownlint
  • make nixie

https://chatgpt.com/codex/tasks/task_e_687296d1a28483229250d4c38fd7db10

Summary by Sourcery

Add support for ‘phony’ and ‘always’ target flags with a shorthand ‘actions’ list and update IR generation, Ninja synthesis, and documentation accordingly

New Features:

  • Introduce ‘phony’ and ‘always’ boolean flags on build targets
  • Add an optional ‘actions’ list that treats entries as phony targets

Enhancements:

  • Propagate ‘phony’ and ‘always’ flags through IR generation and Ninja file synthesis

Documentation:

  • Document the ‘phony’ and ‘always’ flags and the new ‘actions’ block in netsuke-design.md
  • Add a task for supporting these flags in the project roadmap

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 12, 2025

Reviewer's Guide

This PR extends the design documentation to cover new phony and always boolean flags and an optional actions list, showing how they integrate into the AST, IR generation, and Ninja synthesis, and adds corresponding tasks to the project roadmap.

Class diagram for updated NetsukeManifest and Target structs

classDiagram
    class NetsukeManifest {
        Vec~Rule~ rules
        Vec~Target~ actions
        Vec~Target~ targets
        Vec~String~ defaults
    }
    class Target {
        String name
        Vec~String~ deps
        Vec~String~ order_only_deps
        String rule
        HashMap~String, String~ vars
        bool phony
        bool always
    }
    NetsukeManifest "1" -- "*" Rule : contains
    NetsukeManifest "1" -- "*" Target : actions
    NetsukeManifest "1" -- "*" Target : targets
Loading

Class diagram for updated BuildEdge struct

classDiagram
    class BuildEdge {
        Vec~PathBuf~ outputs
        Vec~PathBuf~ implicit_outputs
        Vec~PathBuf~ inputs
        Vec~PathBuf~ implicit_deps
        Vec~PathBuf~ order_only_deps
        bool phony
        bool always
    }
Loading

File-Level Changes

Change Details Files
Document phony, always, and actions in the design guide
  • Define phony and always flags with default behaviors
  • Describe actions list as shorthand for phony targets
  • Update target definition section to reference actions shorthand
  • Augment AST snippet with actions, phony, and always fields
  • Modify IR generation and Ninja synthesis sections to mention flag handling
docs/netsuke-design.md
Add roadmap entries for flags and actions support
  • Insert checklist item for phony and always flags on targets
  • Add item to support parsing of optional actions list
docs/roadmap.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 12, 2025

Summary by CodeRabbit

  • Documentation
    • Updated design documentation to describe new actions list and phony/always flags for build targets.
    • Revised roadmap to reflect support for phony and always flags and the new actions list in manifests.

Summary by CodeRabbit

  • Documentation
    • Expanded documentation to describe new phony and always attributes for build targets.
    • Added details on the new actions list for defining secondary build targets, treated as phony by default.
    • Updated roadmap to reflect support for phony and always flags and the new actions list in manifest parsing.

Walkthrough

Extend the Netsuke build system design and roadmap documentation to introduce two new boolean target attributes, phony and always, and a new top-level actions list for phony targets. Update the Rust data structures and Ninja file generation logic to support these attributes and the new manifest structure.

Changes

File(s) Change Summary
docs/netsuke-design.md Document new phony and always attributes, and the actions list; describe their semantics.
src/ast.rs, src/ir.rs Add phony and always fields to Target and BuildEdge; add actions to NetsukeManifest.
docs/roadmap.md Update roadmap to include phony, always, and actions support in manifest parsing.

Poem

New flags arise—phony and true,
Always running, just for you!
Actions leap from docs to code,
Ninja’s rules now overload.
Build with flair, no more delay,
Netsuke’s future paves the way!
🛠️✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 23ed457 and b652aa3.

📒 Files selected for processing (1)
  • docs/netsuke-design.md (9 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md
**/*.md

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md

⚙️ CodeRabbit Configuration File

🪛 LanguageTool
docs/netsuke-design.md

[uncategorized] ~156-~156: Loose punctuation mark.
Context: ...a Ninja build statement.3 - actions: A secondary list of build targets. Any ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~216-~216: Loose punctuation mark.
Context: ...ore rendering other sections. - phony: When set to true, the target runs whe...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~216-~216: Possible missing comma found.
Context: ...true, the target runs when explicitly requested even if a file with the same name exi...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~219-~219: Loose punctuation mark.
Context: ...he default value is false. - always: When set to true, the target runs on ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~219-~219: Possible missing comma found.
Context: ...set to true, the target runs on every invocation regardless of timestamps or dependenc...

(AI_HYDRA_LEO_MISSING_COMMA)

🔇 Additional comments (4)
docs/netsuke-design.md (4)

351-358: Doc comments for phony / always look good.


638-663: IR struct comments correctly introduce new flags.


677-685: AST-to-IR bullet cleanly explains new behaviour.


726-729: Ninja synthesis section now proposes a valid always-run strategy.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch codex/extend-target-design-with-phony-and-always-flags

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

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

Hey @leynos - I've reviewed your changes and found some issues that need to be addressed.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 7

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7eea95e and b42f147.

📒 Files selected for processing (2)
  • docs/netsuke-design.md (7 hunks)
  • docs/roadmap.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md
**/*.md

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md

⚙️ CodeRabbit Configuration File

🪛 LanguageTool
docs/roadmap.md

[uncategorized] ~22-~22: Possible missing comma found.
Context: ...t phony and always boolean flags on targets and parse an optional actions lis...

(AI_HYDRA_LEO_MISSING_COMMA)

docs/netsuke-design.md

[uncategorized] ~149-~149: Loose punctuation mark.
Context: ...ore rendering other sections. - phony: When set to true, the target runs whe...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~149-~149: Possible missing comma found.
Context: ...true, the target runs when explicitly requested even if a file with the same name exi...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~152-~152: Loose punctuation mark.
Context: ...he default value is false. - always: When set to true, the target runs on ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~152-~152: Possible missing comma found.
Context: ...set to true, the target runs on every invocation regardless of timestamps or dependenc...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~155-~155: Loose punctuation mark.
Context: ...The default value is false. - rules: A list of rule definitions. Each rule i...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~158-~158: Loose punctuation mark.
Context: ...s to a Ninja rule block.2 - targets: The primary list of build targets. Each...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~162-~162: Loose punctuation mark.
Context: ...a Ninja build statement.3 - actions: A secondary list of build targets. Any ...

(UNLIKELY_OPENING_PUNCTUATION)

Comment thread docs/roadmap.md
Comment on lines +22 to +24
- [ ] Support `phony` and `always` boolean flags on targets and parse an
optional `actions` list that treats each entry as a `phony` target.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Wrap the new bullet to ≤ 80 columns and add the serial comma.

The added bullet exceeds the 80-column soft limit and omits the Oxford comma mandated by the style guide. Re-wrap and punctuate correctly.

-  - [ ] Support `phony` and `always` boolean flags on targets and parse an
-    optional `actions` list that treats each entry as a `phony` target.
+  - [ ] Support `phony` and `always` boolean flags on targets, and parse an
+    optional `actions` list that treats each entry as a `phony` target.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- [ ] Support `phony` and `always` boolean flags on targets and parse an
optional `actions` list that treats each entry as a `phony` target.
- [ ] Support `phony` and `always` boolean flags on targets, and parse an
optional `actions` list that treats each entry as a `phony` target.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~22-~22: Possible missing comma found.
Context: ...t phony and always boolean flags on targets and parse an optional actions lis...

(AI_HYDRA_LEO_MISSING_COMMA)

🤖 Prompt for AI Agents
In docs/roadmap.md around lines 22 to 24, the new bullet point exceeds 80
columns and lacks the serial (Oxford) comma. Reformat the bullet text to wrap
lines at or below 80 characters and add the serial comma before the last item in
the list to comply with the style guide.

Comment thread docs/netsuke-design.md
Comment thread docs/netsuke-design.md
Comment thread docs/netsuke-design.md
Comment thread docs/netsuke-design.md
Comment on lines +317 to 319
pub actions: Vec<Target>,

pub targets: Vec<Target>,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Document the default semantics for actions directly in the struct doc-comment.

Readers jumping to the code block should not have to infer behaviour from
earlier prose. Add a short comment beside the new actions field.

-    #[serde(default)]
-    pub actions: Vec<Target>,
+    /// A second target list; every entry is implicitly `{ phony: true }`.
+    #[serde(default)]
+    pub actions: Vec<Target>,
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
pub actions: Vec<Target>,
pub targets: Vec<Target>,
/// A second target list; every entry is implicitly `{ phony: true }`.
#[serde(default)]
pub actions: Vec<Target>,
pub targets: Vec<Target>,
🤖 Prompt for AI Agents
In docs/netsuke-design.md around lines 317 to 319, the new `actions` field lacks
an inline comment explaining its default semantics. Add a brief comment directly
beside the `actions` field in the struct to clearly document its default
behavior, so readers can understand it immediately without referring back to
earlier text.

Comment thread docs/netsuke-design.md Outdated
Comment on lines +149 to +154
- `phony`: When set to `true`, the target runs when explicitly requested even if
a file with the same name exists. The default value is `false`.

- `always`: When set to `true`, the target runs on every invocation regardless
of timestamps or dependencies. The default value is `false`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Re-wrap the phony/always bullets to honour the 80-column rule.

Both bullets run past the prescribed width. Re-flow to two lines apiece.

- - `phony`: When set to `true`, the target runs when explicitly requested even if
-   a file with the same name exists. The default value is `false`.
- - `always`: When set to `true`, the target runs on every invocation regardless
-   of timestamps or dependencies. The default value is `false`.
+ - `phony`: When `true`, the target runs when explicitly requested even if a
+   file with the same name exists. The default value is `false`.
+ - `always`: When `true`, the target runs on every invocation, regardless of
+   timestamps or dependencies. The default value is `false`.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- `phony`: When set to `true`, the target runs when explicitly requested even if
a file with the same name exists. The default value is `false`.
- `always`: When set to `true`, the target runs on every invocation regardless
of timestamps or dependencies. The default value is `false`.
- `phony`: When `true`, the target runs when explicitly requested even if a
file with the same name exists. The default value is `false`.
- `always`: When `true`, the target runs on every invocation, regardless of
timestamps or dependencies. The default value is `false`.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~149-~149: Loose punctuation mark.
Context: ...ore rendering other sections. - phony: When set to true, the target runs whe...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~149-~149: Possible missing comma found.
Context: ...true, the target runs when explicitly requested even if a file with the same name exi...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~152-~152: Loose punctuation mark.
Context: ...he default value is false. - always: When set to true, the target runs on ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~152-~152: Possible missing comma found.
Context: ...set to true, the target runs on every invocation regardless of timestamps or dependenc...

(AI_HYDRA_LEO_MISSING_COMMA)

🤖 Prompt for AI Agents
In docs/netsuke-design.md around lines 149 to 154, the bullet points for `phony`
and `always` exceed the 80-column width limit. Reformat each bullet point so
that the text wraps neatly within 80 characters per line, splitting the
descriptions into two lines each while preserving the original meaning and
clarity.

Comment thread docs/netsuke-design.md Outdated
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (6)
docs/netsuke-design.md (6)

156-158: Wrap actions bullet to ≤ 80 columns and drop literal braces.

The line still breaches the project’s 80-column rule and repeats the literal struct-style braces that prose should avoid. Re-flow it and phrase the defaults in plain English.

- - `actions`: A secondary list of build targets. Any target placed here is
-   treated as `{ phony: true, always: false }` by default.
+ - `actions`: A secondary list of build targets. Each entry is treated as a
+   phony target that does not run on every invocation by default.

218-223: Re-wrap phony/always bullets to 80 columns.

The bullets still exceed the mandated width and replicate the “When set to true” boiler-plate. Adopt the earlier suggestion verbatim.

- - `phony`: When set to `true`, the target runs when explicitly requested even if
-   a file with the same name exists. The default value is `false`.
- - `always`: When set to `true`, the target runs on every invocation regardless
-   of timestamps or dependencies. The default value is `false`.
+ - `phony`: When `true`, the target runs even if an output file already exists.
+   Default: `false`.
+ - `always`: When `true`, the target runs on every build regardless of
+   timestamps or dependencies. Default: `false`.

316-318: Add a doc-comment above actions field.

Maintain parity with other documented fields and surface semantics to IDEs.

-    #[serde(default)]
-    pub actions: Vec<Target>,
+    /// A secondary target list whose entries are implicitly phony.
+    #[serde(default)]
+    pub actions: Vec<Target>,

354-359: Document phony and always fields.

Doc-comments remain missing despite prior feedback.

-    #[serde(default)]
-    pub phony: bool,
-
-    #[serde(default)]
-    pub always: bool,
+    /// Run even when a file with the same name already exists.
+    #[serde(default)]
+    pub phony: bool,
+
+    /// Run on every invocation, ignoring timestamps.
+    #[serde(default)]
+    pub always: bool,

656-660: Update struct-level summary to mention phony and always.

The field-level docs are welcome, yet the opening summary above BuildEdge still references only inputs/outputs. Append one sentence so autogenerated docs stay accurate.


724-726: Remove incorrect -t run advice for always targets.

-t run is a Ninja CLI flag, not a build-file directive, and embedding it will break builds. Describe a supported strategy instead:

-   If `phony` is `true`, use Ninja's built-in `phony` rule. If `always` is
-   `true`, append the `-t run` invocation so the command executes every time.
+   If `phony` is `true`, emit a phony build edge with no outputs.  
+   If `always` is `true`, either emit a dummy output that always depends on an
+   `alwaysdirty` target or declare a phony rule with no outputs so Ninja
+   re-executes the step on every build.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b42f147 and 23ed457.

📒 Files selected for processing (1)
  • docs/netsuke-design.md (8 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
docs/**/*.md

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md
**/*.md

Instructions used from:

Sources:
📄 CodeRabbit Inference Engine

  • AGENTS.md

⚙️ CodeRabbit Configuration File

🪛 LanguageTool
docs/netsuke-design.md

[uncategorized] ~156-~156: Loose punctuation mark.
Context: ...a Ninja build statement.3 - actions: A secondary list of build targets. Any ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~218-~218: Loose punctuation mark.
Context: ...ore rendering other sections. - phony: When set to true, the target runs whe...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~218-~218: Possible missing comma found.
Context: ...true, the target runs when explicitly requested even if a file with the same name exi...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~221-~221: Loose punctuation mark.
Context: ...he default value is false. - always: When set to true, the target runs on ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~221-~221: Possible missing comma found.
Context: ...set to true, the target runs on every invocation regardless of timestamps or dependenc...

(AI_HYDRA_LEO_MISSING_COMMA)

Comment thread docs/netsuke-design.md Outdated
@leynos leynos merged commit c5ae2a1 into main Jul 12, 2025
1 check was pending
@leynos leynos deleted the codex/extend-target-design-with-phony-and-always-flags branch July 12, 2025 19:20
@coderabbitai coderabbitai Bot mentioned this pull request Jul 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant