feat: add executable flag to pixi run

[kajal-jotwani]

Description

Adds a --executable (-x) flag to pixi run to allow running executables even when a task with the same name exists.

Fixes #5128

How Has This Been Tested?

AI Disclosure

• This PR contains AI-generated content.
  • I have tested any AI-generated content in my PR.
  • I take responsibility for any AI-generated content in my PR.

Tools: {e.g., Claude, Codex, GitHub Copilot, ChatGPT, etc.}

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added sufficient tests to cover my changes.
• I have verified that changes that would impact the JSON schema have been made in schema/model.py.

[baszalmstra]

This is a bit of an anti-pattern. If we have multiple booleans as arguments it becomes hard to distinguish what the false indicates. Instead its good practice to introduce an enum. E.g. PreferExecutable with variants like Always, Never, IfNoTask or something along those lines.

[kajal-jotwani]

Thanks for the suggestion! I've updated the implementation to use a PreferExecutable enum with Never and Always variants instead of bool. I didn't include an IfNoTask variant since that behavior is already the default when using PreferExecutable::Never the code naturally falls back to executing the command when no matching task is found.

[baszalmstra]

Is this correct? The implementation would suggest it falls back to executing an executable. With Never I would suspect that only tasks are run.

[kajal-jotwani]

You’re right the current implementation falls back to executing it as an executable if no task exists. I’ll rename the enum to something clearer like TaskFirst to better reflect the actual behavior.

[ruben-arts]

Suggested change

	/// Prefer running the command as an executable instead of a Pixi task
	/// when both share the same name. Short: -x
	/// Execute command without matching with a task name.
	///
	/// Usefull when a task name and an executable have the same name.

I feel that "prefer" sends a signal that it might still use tasks. But IIUC it will not try any task logic anymore.

[ruben-arts]

Suggested change

	/// Controls whether to prefer resolving commands as executables over Pixi tasks
	#[derive(Debug, Clone, Copy, PartialEq, Eq)]
	pub enum PreferExecutable {
	/// Try to resolve as a Pixi task first, fall back to executable if no task found (default)
	TaskFirst,
	/// Always treat as an executable, skip task resolution
	Always,
	}
	impl Default for PreferExecutable {
	fn default() -> Self {
	Self::TaskFirst
	}
	}
	/// Controls whether to prefer resolving commands as executables over Pixi tasks
	#[derive(Debug, Clone, Copy, PartialEq, Eq, Default)]
	pub enum PreferExecutable {
	/// Try to resolve as a Pixi task first, fall back to executable if no task found
	#[default]
	TaskFirst,
	/// Always treat as an executable, skip task resolution
	Always,
	}

Rust (>1.62) has the ability to use the default derive so you don't have to write the default implementation yourself. We try to use this as much as possible

[ruben-arts]

It would be good to add a test to check if the logic keeps working when you set it to always.

[kajal-jotwani]

@ruben-arts thanks for the review! I have addressed all the comments.

[ruben-arts]

Thank you! It works for me now!

[ruben-arts]

As all @baszalmstra 's reviews are processed I'm merging this in.