Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: PSModule/GitHub
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 34c013c
Choose a base ref
...
head repository: PSModule/GitHub
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: a11a390
Choose a head ref
  • 1 commit
  • 335 files changed
  • 1 contributor

Commits on Oct 14, 2025

  1. 🩹 [Patch]: Add Linter settings + fix documentation structure (#535)

    ## Description
    
    This pull request primarily fixes the documentation of PowerShell
    functions by adding PowerShell-formatted code blocks to the `.EXAMPLE`
    sections, due to upgrading from `platyPS` to
    `Microsoft.PowerShell.PlatyPS`. Additionally, it introduces
    configuration changes for linters and minor formatting corrections.
    
    Documentation improvements:
    
    * Added PowerShell-formatted code blocks to the `.EXAMPLE` sections of
    many function files in `src/functions/*`. This was needed to retain the
    code blocks in the examples, as `Microsoft.PowerShell.PlatyPS` lets the
    user configure this.
    
    Linter and configuration updates:
    
    * Added a `Linter` section to `.github/PSModule.yml` to explicitly
    disable several validation checks, such as `VALIDATE_BIOME_FORMAT` and
    `VALIDATE_POWERSHELL`.
    * Fixed a minor formatting issue in `.github/linters/.markdown-lint.yml`
    by changing double quotes to single quotes for the `MD026.punctuation`
    setting. This was also due to `Microsoft.PowerShell.PlatyPS` adding H3
    for types which can be same for `.INPUTS` and `.OUTPUTS`.
    
    Encoding and formatting corrections:
    
    * Added or corrected UTF-8 BOM in some PowerShell files to ensure proper
    encoding.
    MariusStorhaug authored Oct 14, 2025
    Configuration menu
    Copy the full SHA
    a11a390 View commit details
    Browse the repository at this point in the history
Loading