Skip to content

Upgraded to GitHub Copilot Pro #62

Open

Description

@johnharolddunn

Ist payment was asking $48 per year...paid
Dmitry Neverov (@nd) payment was for Pro Plus at about $40 per month.

These conflict when trying to go from GitHub Copilot free to any GitHub available (presuming one is Pro) when trying to get the following to work...

Desktop PowerShell script cleanup plan

Problem and approach

Add a short, accurate, script-specific explanation note to each applicable PowerShell script under C:\Users\johnh\OneDrive\Desktop, and consolidate only scripts whose behavior and intended use are demonstrably the same. Preserve distinct behaviors and all callers, especially the dynamic In-Tray menu and the TiCalc menu. Do not remove any original until its replacement has been checked and validated.

This is a folder-backed workspace without Git history or diff support. The current request is for findings and approval only; no script has been edited, run, moved, or deleted.

Inventory and exact scope

The recursive inventory contains 472 .ps1 files and no .psm1 or .psd1 files:

Location under Desktop .ps1 count
Desktop root 150
In-Tray 169
TiCalc 25
Desktop 74
Logs 40
Desktop Tools 7
Private-Network-Remote 5
Calc 1
Games 1
Total 472

Implementation after approval

  1. Re-read all 472 in-scope scripts and classify each by actual purpose, inputs, outputs, and material side effects. Add a concise, script-specific explanation comment in the file's existing style; do not add generic copy-paste notes. For scripts selected for consolidation, document the validated replacement rather than editing a file scheduled for removal.
  2. Compare only the overlap groups above and any additional overlap established by reading behavior. Prefer retaining one canonical implementation and retargeting its callers over introducing a new abstraction. Keep distinct options and risk controls; do not merge the redirection, cleanup, repair/health, or differing-payload generators without a demonstrated compatible design.
  3. Before any removal, verify the replacement and search the Desktop tree plus relevant batch/cmd launchers for references. Preserve MasterMenu.ps1 and TiCalc menu paths or explicitly update and validate every caller. Confirm the final In-Tray menu still exposes the intended tools.
  4. Validate changed PowerShell files with the PowerShell parser without executing them, check references and menu discovery, and review the final script set for one accurate note per retained script. Do not run repair, registry, deletion, reboot, installation, or other side-effecting scripts as a validation shortcut. Remove an original only after its replacement and references pass these checks.

Notes and risks

The scripts include registry changes, forced process termination, shortcut/recursive deletion, elevation, reboot/shutdown, and system-feature changes. TiCalc analysis may delete and recreate output directories; Sync-TiCalc.ps1 syncs whole trees and resolves timestamp ties in favor of OneDrive, whereas Sync-TnsFiles.ps1 syncs .tns documents. Documentation must state these effects accurately, and validation should remain static unless a script has a safe, isolated test mode.

Implementation progress

  • In-Tray: reviewed all 169 scripts; existing accurate notes were retained and generic/vague notes corrected. Six verified duplicate/compatibility entries were removed, keeping MasterMenu.ps1, Show-Installed-Apps.ps1, and Refresh-OneDrive-Shell.ps1.
  • The In-Tray sync utility now excludes those six retired names, preventing profile copies from restoring them. Static checks confirm all 163 remaining In-Tray scripts have non-generic purpose notes, parse successfully, and the menu still discovers the expected 247 files.
  • TiCalc: reviewed all 25 scripts; three notes were corrected and 22 accurate notes retained. The modified files pass static parser validation.
  • Remaining Desktop-root and subfolder script-note batches, plus final whole-tree validation, are still in progress.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions