Migrate non-related deliverables to its own repo

Assessment

This issue has not been assessed yet.

Description

Contributor guide

Open the contributing guide

First steps

1. Read the whole issue, then the project's contributing guide.
2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
3. Fork the repository and make your change on a branch.
4. Open a pull request that references the issue number.

More from IntelliTect/PSToolbox

• chore: add .gitattributes -- no line-ending normalization, CRLF and mixed endings already committed Open

  Difficulty 2/5 Half a day Newbie friendliness 80/100

  IntelliTect/PSToolbox#119 · Opened Sep 6, 2026

• [3.0] Delete the deprecated IntelliTect.CredentialManager module folder and tests Open
  enhancement

  Difficulty 4/5 3-5 days Newbie friendliness 48/100

  IntelliTect/PSToolbox#118 · Opened May 18, 2026

• Cannot publish/unlist modules in PSGallery: `MarkMichaelis` is not an owner of any `IntelliTect.*` package Open

  Difficulty 5/5 Over a week Newbie friendliness 25/100

  IntelliTect/PSToolbox#117 · 1 comment · Opened May 18, 2026

• According to readme, azure pipeline has never been built Open

  Difficulty 3/5 1-2 days Newbie friendliness 42/100

  IntelliTect/PSToolbox#112 · Opened Jan 31, 2022

• Pester Tests not working (IntelliTect.Google and IntelliTect.CredentialManager) Open

  Difficulty 3/5 1-2 days Newbie friendliness 35/100

  IntelliTect/PSToolbox#105 · Opened Jun 18, 2021

All issues in IntelliTect/PSToolbox