8000 Revert "Add `-StrictMode` to `Invoke-Command` to allow specifying strict mode when invoking command locally" by SteveL-MSFT · Pull Request #18040 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]
Skip to content

Revert "Add -StrictMode to Invoke-Command to allow specifying strict mode when invoking command locally" #18040

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign 8000 up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 4 commits into from
Sep 12, 2022
Merged

Revert "Add -StrictMode to Invoke-Command to allow specifying strict mode when invoking command locally" #18040

merged 4 commits into from
Sep 12, 2022

Conversation

SteveL-MSFT
Copy link
Member

Reverts #16545

Per #17962 we are removing this experimental feature due to being limited from working remotely and thus has limited value

@SteveL-MSFT
Revert "Add -StrictMode to Invoke-Command to allow specifying str…
ac4460e 
…ict mode when invoking command locally (#16545)"

This reverts commit ed6e058.
@ghost ghost assigned adityapatwardhan Sep 6, 2022
@daxian-dbw daxian-dbw mentioned this pull request Sep 8, 2022
Closed
@pull-request-quantifier-deprecated
Copy link

This PR has 92 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details 

Label      : Small
Size       : +12 -80
Percentile : 36.8%

Total files changed: 5

Change summary by file extension:
.json : +0 -2
.cs : +12 -60
.ps1 : +0 -18

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@adityapatwardhan adityapatwardhan merged commit 944ed54 into master Sep 12, 2022
@adityapatwardhan adityapatwardhan deleted the revert-16545-StrictMode-for-Invoke-Command branch September 12, 2022 18:42
@adityapatwardhan
Copy link
Member

/backport to release/v7.3.0-rc.1

@github-actions github-actions bot mentioned this pull request Sep 12, 2022
Merged
1 task
@ghost
Copy link
ghost commented Sep 20, 2022

🎉v7.3.0-preview.8 has been released which incorporates this pull request.:tada:

Handy links:

@michaeltlombardi michaeltlombardi mentioned this pull request Sep 21, 2022
Closed
2 tasks
@TravisEz13 TravisEz13 mentioned this pull request Sep 30, 2022
Merged
22 tasks
@adityapatwardhan adityapatwardhan added the CL-NotInBuild Indicates that a PR is reverted and not part of the build. label Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@adityapatwardhan adityapatwardhan adityapatwardhan approved these changes

@PaulHigin PaulHigin PaulHigin approved these changes

Assignees

@adityapatwardhan adityapatwardhan

Labels
Backport-7.3.x-Done CL-NotInBuild Indicates that a PR is reverted and not part of the build. Small
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@SteveL-MSFT @adityapatwardhan @PaulHigin @daxian-dbw
0