Skip to content

Commit

Permalink
Merge pull request #50 from Lombiq/issue/OSOE-961
Browse files Browse the repository at this point in the history
OSOE-961: Using codespell instead of the spelling workflow
  • Loading branch information
Piedone authored Feb 19, 2025
2 parents a3e216b + 0e021fe commit 7fce6d7
Show file tree
Hide file tree
Showing 7 changed files with 17 additions and 19 deletions.
2 changes: 2 additions & 0 deletions .codespellrc
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
[codespell]
ignore-words-list += , pullRequest
4 changes: 0 additions & 4 deletions .github/actions/spelling/allow.txt

This file was deleted.

13 changes: 0 additions & 13 deletions .github/workflows/check-spelling.yml

This file was deleted.

13 changes: 13 additions & 0 deletions .github/workflows/codespell.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
name: Codespell

# Runs for PRs opened for any branch, and pushes to the dev branch.
on:
pull_request:
push:
branches:
- dev

jobs:
codespell:
name: Codespell
uses: Lombiq/GitHub-Actions/.github/workflows/codespell.yml@dev
File renamed without changes.
2 changes: 1 addition & 1 deletion Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ As of writing this document [SQL Server in Docker doesn't support Windows authen
## Installing the PowerShell modules

1. Set the PowerShell script execution policy to Unrestricted in order to use any of the scripts. To achieve this run the `Set-ExecutionPolicy Unrestricted` command.
2. Run the `AddPathToPSModulePath.ps1` script (you need admin privileges) to add the root of the repository to the `PSModulePath` environment variable. This will make PowerShell recognise this folder as one of the folders that contain PS modules. You only need to run this once - after that any changes made to these modules will be picked up automatically when a new PS console is opened. **NOTE**: It may be required to restart the PowerShell console, so do that as well.
2. Run the `AddPathToPSModulePath.ps1` script (you need admin privileges) to add the root of the repository to the `PSModulePath` environment variable. This will make PowerShell recognize this folder as one of the folders that contain PS modules. You only need to run this once - after that any changes made to these modules will be picked up automatically when a new PS console is opened. **NOTE**: It may be required to restart the PowerShell console, so do that as well.
3. Enjoy!


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ function Test-VSProjectConsistency
# If the path is a file but not a csproj, then return an error.
if (-not $isPathContainer -and -not $isPathCsproj)
{
Write-Error ('The specified parth is not a folder or a visual studio project file!')
Write-Error ('The specified path is not a folder or a visual studio project file!')
return
}

Expand Down

0 comments on commit 7fce6d7

Please sign in to comment.