diff --git a/.github/workflows/APIs-Tests-on-Linux.yaml b/.github/workflows/APIs-Tests-on-Linux.yaml index 1483d1a..2d49f51 100644 --- a/.github/workflows/APIs-Tests-on-Linux.yaml +++ b/.github/workflows/APIs-Tests-on-Linux.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: api-tests-on-linux: diff --git a/.github/workflows/APIs-Tests-on-MacOS.yaml b/.github/workflows/APIs-Tests-on-MacOS.yaml index f09b81a..3a6db05 100644 --- a/.github/workflows/APIs-Tests-on-MacOS.yaml +++ b/.github/workflows/APIs-Tests-on-MacOS.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: api-tests-on-macos: diff --git a/.github/workflows/APIs-Tests-on-Windows.yaml b/.github/workflows/APIs-Tests-on-Windows.yaml index 4b8f5e1..565d1b5 100644 --- a/.github/workflows/APIs-Tests-on-Windows.yaml +++ b/.github/workflows/APIs-Tests-on-Windows.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: api-tests-on-windows: diff --git a/.github/workflows/Components-Tests-on-Linux.yaml b/.github/workflows/Components-Tests-on-Linux.yaml index 029e150..3034200 100644 --- a/.github/workflows/Components-Tests-on-Linux.yaml +++ b/.github/workflows/Components-Tests-on-Linux.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: component-tests-on-linux: diff --git a/.github/workflows/Components-Tests-on-MacOS.yaml b/.github/workflows/Components-Tests-on-MacOS.yaml index 4aa6829..3613dcd 100644 --- a/.github/workflows/Components-Tests-on-MacOS.yaml +++ b/.github/workflows/Components-Tests-on-MacOS.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: component-tests-on-macos: diff --git a/.github/workflows/Components-Tests-on-Windows.yaml b/.github/workflows/Components-Tests-on-Windows.yaml index 88edcec..63a942c 100644 --- a/.github/workflows/Components-Tests-on-Windows.yaml +++ b/.github/workflows/Components-Tests-on-Windows.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: component-tests-on-windows: diff --git a/.github/workflows/Intsallation-Tests-on-Linux.yaml b/.github/workflows/Intsallation-Tests-on-Linux.yaml index d8205da..3ea652d 100644 --- a/.github/workflows/Intsallation-Tests-on-Linux.yaml +++ b/.github/workflows/Intsallation-Tests-on-Linux.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: installation-tests-on-linux: diff --git a/.github/workflows/Intsallation-Tests-on-MacOS.yaml b/.github/workflows/Intsallation-Tests-on-MacOS.yaml index eb162bb..76042c6 100644 --- a/.github/workflows/Intsallation-Tests-on-MacOS.yaml +++ b/.github/workflows/Intsallation-Tests-on-MacOS.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: installation-tests-on-macos: diff --git a/.github/workflows/Intsallation-Tests-on-Windows.yaml b/.github/workflows/Intsallation-Tests-on-Windows.yaml index f6fb788..0004a3d 100644 --- a/.github/workflows/Intsallation-Tests-on-Windows.yaml +++ b/.github/workflows/Intsallation-Tests-on-Windows.yaml @@ -4,6 +4,7 @@ on: push: branches: - main + - dev jobs: installation-tests-on-windows: diff --git a/CONTRIBUTION.md b/CONTRIBUTION.md index c721951..63da566 100644 --- a/CONTRIBUTION.md +++ b/CONTRIBUTION.md @@ -12,7 +12,7 @@ Here are some formative rules for this module's development: - **Coding:** - **Variable Naming**: `snake_case` is used to indicate private variables while `PascalCase` is used for non-private variables. So, in code style consistency, please consider the above rule. - - **Comments** : This module refers to many cmdlets in [Microsoft.PowerShell.Management](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/?view=powershell-7.3), such as [`Get-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-item?view=powershell-7.3), [`Copy-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/copy-item?view=powershell-7.3) and [`New-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.3). Then, we decided to use a similar comment style as theirs. The following are some specific rules:: + - **Comments**: This module refers to many cmdlets in [Microsoft.PowerShell.Management](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/?view=powershell-7.3), such as [`Get-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/get-item?view=powershell-7.3), [`Copy-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/copy-item?view=powershell-7.3) and [`New-Item`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.management/new-item?view=powershell-7.3). Then, we decided to use a similar comment style as theirs. The following are some specific rules:: - `.SYNOPSIS` and `.DESCRIPTION` are both used to describe the function's usage and details. - `.DESCRIPTION` is mandatory while `.SYNOPSIS` is optional. - `.SYNOPSIS` is a brief description of key points, but `.DESCRIPTION` is a detailed description with rationales and ideas. @@ -22,6 +22,6 @@ Here are some formative rules for this module's development: - `.LINK` is used to post crucial links in the format `[aaaa](bbb)` without any other words. - Given that, at the moment, widescreen monitors are not uncommon, don't actively make length constraints on comments, and don't manually split lines in the middle of sentences. The task of constraining the length of comments can be left to editors and automation tools and not reflected in the source code. - **Internal Behaviors:** - - **Logging:**: The principle is that when making logs, the logs will be written into files anyway. If a log needs to be displayed in the console, it will be done as a `Verbose` message. The private function `Write-FileLog` should only be used in the private function `Write-Log`, and the latter is the only logging function in all components. Also, the latter is not an API function for normal users. + - **Logging**: The principle is that when making logs, the logs will be written into files anyway. If a log needs to be displayed in the console, it will be done as a `Verbose` message. The private function `Write-FileLog` should only be used in the private function `Write-Log`, and the latter is the only logging function in all components. Also, the latter is not an API function for normal users. - **Objects to Operate:** - - **Hardlinks:**: Although hard links can sometimes be considered normal files, in this module, it is recommended to restrict any `copy-` or `move-` operations on hard links to avoid potential problems. \ No newline at end of file + - **Hardlinks**: Although hard links can sometimes be considered normal files, in this module, it is recommended to restrict any `copy-` or `move-` operations on hard links to avoid potential problems. \ No newline at end of file diff --git a/Module/PSComputerManagementZp.psm1 b/Module/PSComputerManagementZp.psm1 index 5b46905..dbc9bf2 100644 --- a/Module/PSComputerManagementZp.psm1 +++ b/Module/PSComputerManagementZp.psm1 @@ -31,7 +31,7 @@ $ModuleInfo = @{ $ModuleSettings = @{ RootModule = "$($ModuleInfo.ModuleName).psm1" CompatiblePSEditions = @('Desktop', 'Core') - ModuleVersion = '0.1.3' + ModuleVersion = '0.1.4' Prerelease = '' Author = 'Pu Zhao' Description = 'A PowerShell module that derives from personal scenarios, can help users configure the Windows PCs easily to realize many useful operations, involving authorization, env, links, proxy, etc. Some features are also available on WSL2, Linux, and MacOS. See [PSComputerManagementZp](https://github.com/Zhaopudark/PSComputerManagementZp) for more details.' diff --git a/RELEASE.md b/RELEASE.md index 18cd14a..6517534 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -1,4 +1,6 @@ # PSComputerManagementZp 0.1.x +## Release 0.1.4 +On working... ## Release 0.1.3 - Add `Register-AndBackupEnvItemForConda` and `Unregister-WithBackupEnvItemForConda` in `Assister.ThirdParty.ps1` to help users to register and unregister the environment variables for `Conda` with backup. See [Conda | Saving environment variables](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#saving-environment-variables) and [the source code](https://github.com/Zhaopudark/PSComputerManagementZp/blob/main/Module/Public/Assister.ThirdParty.ps1) for more details. ## Release 0.1.2