-
Notifications
You must be signed in to change notification settings - Fork 8.3k
PowerShell Scripts require .ps1 extension #1103
Copy link
Copy link
Closed
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productOS-LinuxResolution-FixedThe issue is fixed.The issue is fixed.Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability
Milestone
Metadata
Metadata
Assignees
Labels
Committee-ReviewedPS-Committee has reviewed this and made a decisionPS-Committee has reviewed this and made a decisionIssue-BugIssue has been identified as a bug in the productIssue has been identified as a bug in the productOS-LinuxResolution-FixedThe issue is fixed.The issue is fixed.Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability
Scripts (on linux) don't function unless they have the extension
.ps1(generally, languages do not require specific extensions in Linux when using shebang to start them#! /usr/bin/powershellSteps to reproduce
File:
myscript#!/usr/bin/powershell echo hiExpected behavior
On linux, this should work even if the extension isn't
.ps1Actual behavior
EDIT
it turns out it didn't hang, it fails:
Environment data
v0.4.0