GitHub Automation and Commands

🚀 Shelvera CI/CD Pipeline Stress Test

Build copy-ready PowerShell commands for safely validating or intentionally triggering branch-based CI/CD pipelines across Shelvera repositories. The recommended workflow is always preview first, review the results, and then execute only when the preview is clean.

1. Generate Commands

# AnchorCommands prepared

Shelvera Promotion Command Builder

Generate safe, copy-ready PowerShell commands for validating or intentionally triggering CI/CD pipelines across your Shelvera repositories.

Safe PreviewForced Pipeline Stress Test1 Selected Repository

Script Location

Used to generate the navigation and help commands.

Script Folder

Folder containing your PowerShell automation script.

Script File Name

Your command reference examples execute ts_git_commit_automation.ps1. Change this value if you renamed the file.

Execution Mode

Invalid mode combinations are prevented because you select exactly one mode.

OperationSafe preview / validation onlyActual execution

Generates -DryRun. No commits, merges or pushes occur.

Promotion BehaviorForced CI/CD stress testNormal promotion only when needed

Includes -ForcePipelineStressTest and deliberately tests pipeline triggering.

Timing and Failure Handling

Control how aggressively the script promotes branches and processes repositories.

Branch Delay Seconds

Wait before each branch promotion.

Repository Delay Seconds

Wait before the next repository.

Stop processing after the first failureRecommended for actual runs. Adds -StopOnFailure to execution commands.Include delay arguments in preview commandsOptional. Delays matter primarily during actual execution, but this lets you mirror the complete intended run configuration in previews.

Repository Selection

Choose repositories once and let the page generate the exact -RepoIds argument.

Repository ScopeSelected repositories onlyAll repositories without promptInteractive repository prompt

Only the checked repositories are included in the generated command.

Useful presets

1. ts-001Parent Repository2. ts-gw-srvc-001Gateway Service3. ts-log-srvc-001Logging Service4. ts-bill-srvc-001Billing Service5. ts-conf-srvc-001Configuration Service6. ts-data-srvc-001Data Service7. ts-file-srvc-001File Service8. ts-notif-srvc-001Notification Service9. ts-probe-srvc-001Probe Service10. ts-data-job-001Data Job11. ts-db-001Database Migrations12. ts-web-ui-001Public Web UI13. ts-admin-ui-001Admin UI14. ts-alloy-secret-agent-001Alloy Secret Agent

Optional and Advanced Settings

Use these only when you need custom logs or a repository flow different from the Shelvera defaults.

Use custom transcript directoryAdds -TranscriptDirectory to every generated command.Include explicit branch and remote overridesNormally keep this off. Enable only when the target repository uses non-standard branches or a different Git remote.

Generated Run Summary

Review this summary before copying an actual execution command.

Repository Scope

14. ts-alloy-secret-agent-001

Branch Flow

local → dev → qa → prod → main → local

Pipeline Timing

10 seconds between branch promotions; 20 seconds between repositories.

Selected Behavior

Shows what a forced marker-commit pipeline run would do without creating commits, merging or pushing.

Safe preview selected. This generated command uses -DryRun and does not create commits, merge branches, push changes or trigger pipelines.

Navigate to Script Folder

Run this first if your PowerShell terminal is not already inside the automation folder.

Set-Location -Path "C:\Users\Manoj\OneDrive\MyDocuments-OneDrive\Notepad++ Notes\Shelvera Notes\Git Comit Automation"

Your Generated Preview Command

Copy and run this safe validation command.

.\ts_git_commit_automation.ps1 `
    -RepoIds 14 `
    -DryRun `
    -ForcePipelineStressTest

Matching Actual Command After Successful Preview

This command creates a marker commit and deliberately promotes it through the configured branches for pipeline testing.

.\ts_git_commit_automation.ps1 `
    -RepoIds 14 `
    -CreateTestCommit `
    -ForcePipelineStressTest `
    -BranchDelaySeconds 10 `
    -RepoDelaySeconds 20 `
    -StopOnFailure

Show the command matching the currently selected operation only

Current Selection: Preview

.\ts_git_commit_automation.ps1 `
    -RepoIds 14 `
    -DryRun `
    -ForcePipelineStressTest

Show generated PowerShell help commands

Detailed Script Help

Get-Help .\ts_git_commit_automation.ps1 -Detailed

Script Examples Only

Get-Help .\ts_git_commit_automation.ps1 -Examples

2. Safety Rules

# AnchorSafety rules reviewed

Before running an actual promotion or pipeline stress test, confirm the following:

• The script stages and commits only pipeline-stress-test.txt.

• It does not execute git add . or git add -A.

• Real source-code changes must already be committed to local.

• Unexpected downstream branch commits block that repository as REVIEW REQUIRED.

• Every processed repository returns to the local branch after execution.

• Actual forced runs deliberately create a marker commit and may trigger multiple CI/CD pipelines.

Recommended rule

Always run the generated Preview Command first. Run the matching Actual Execution Command only after the preview completes without a failed or REVIEW REQUIRED repository.

3. Parameter Guide

# AnchorParameters understood

Input on this page	Generated parameter	Purpose
Operation: Safe preview	-DryRun	Performs validation and branch comparison without commits, merges or pushes.
Operation: Actual execution	-CreateTestCommit	Creates the marker commit when the configured promotion requires it.
Promotion Behavior: Forced CI/CD stress test	-ForcePipelineStressTest	Forces a marker commit and full promotion even when branches are already synchronized.
Repository Scope / Repository Checkboxes	-RepoIds	Limits the run to selected repositories and avoids the runtime selection prompt.
Branch Delay Seconds	-BranchDelaySeconds	Wait time before each branch promotion.
Repository Delay Seconds	-RepoDelaySeconds	Wait time before processing the next repository after pipeline-triggering work.
Stop processing after first failure	-StopOnFailure	Stops after a failure or REVIEW REQUIRED result. Recommended for actual runs.
Custom Transcript Directory	-TranscriptDirectory	Places transcript logs in your chosen folder.
Advanced Branch Overrides	-LocalBranch, -DevBranch, -QaBranch, -ProdBranch, -MainBranch, -RemoteName	Supports a compatible repository whose branch or remote naming differs from Shelvera defaults.

Invalid combinations avoided by this page

The command builder never generates -DryRun together with -CreateTestCommit, and it never generates a command without one of these required execution modes.

4. Repository Catalog

# AnchorRepository selection verified

The command builder preserves the repository catalog order used by the PowerShell automation.

1. ts-001

Parent Repository

D:\code\ts-001-org\ts-001

2. ts-gw-srvc-001

Gateway Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-gw-srvc-001

3. ts-log-srvc-001

Logging Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-log-srvc-001

4. ts-bill-srvc-001

Billing Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-bill-srvc-001

5. ts-conf-srvc-001

Configuration Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-conf-srvc-001

6. ts-data-srvc-001

Data Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-data-srvc-001

7. ts-file-srvc-001

File Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-file-srvc-001

8. ts-notif-srvc-001

Notification Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-notif-srvc-001

9. ts-probe-srvc-001

Probe Service

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-probe-srvc-001

10. ts-data-job-001

Data Job

D:\code\ts-001-org\ts-001\Jobs\ts-data-job-001

11. ts-db-001

Database Migrations

D:\code\ts-001-org\ts-001\DBMigrations\ts-db-001

12. ts-web-ui-001

Public Web UI

D:\code\ts-001-org\ts-001\Web\Shelvera\ts-web-ui-001

13. ts-admin-ui-001

Admin UI

D:\code\ts-001-org\ts-001\Web\AdminUI\ts-admin-ui-001

14. ts-alloy-secret-agent-001

Alloy Secret Agent

D:\code\ts-001-org\ts-001\MicroServices (Web APIs)\ts-alloy-secret-agent-001

5. Recommended Operating Sequence

# AnchorRun sequence followed

5.1 First actual forced pipeline test

Start with a single low-risk repository selection:

1. Keep the default preset: Safe Starter: Alloy Agent.
2. Keep Promotion Behavior as Forced CI/CD stress test.
3. Run the generated Preview Command.
4. Review the console summary and transcript log.
5. Run the generated Actual Execution Command only after the preview is clean.

5.2 Selected repository pipeline test

Choose a preset or select repositories individually. Suitable examples include:

• Core APIs for service-layer deployments.
• Data Platform for Data, File, Job and database migration validation.
• Web Applications for public website and Admin UI deployment validation.
• Observability / Security for Log, Probe and Alloy Secret Agent validation.

5.3 Full platform pipeline test

For a complete test:

1. Select All Repositories.
2. Generate and run the preview command.
3. Check for failures or REVIEW REQUIRED statuses.
4. Monitor the relevant CI/CD pipelines and application environments.
5. Run the actual execution command only after the preview is successful.

Full forced execution

A forced all-repository run intentionally triggers pipeline activity across the full Shelvera solution. Keep sensible branch and repository delays unless you explicitly need a rapid-load test.

6. Quick Decision Guide

# AnchorExecution choice confirmed

Goal	Recommended Inputs
Check safety and branch status only	Operation: Safe preview; Promotion Behavior: Normal promotion
Preview an intentional CI/CD stress test	Operation: Safe preview; Promotion Behavior: Forced CI/CD stress test
Promote only repositories with real committed branch differences	Operation: Actual execution; Promotion Behavior: Normal promotion
Deliberately trigger CI/CD pipelines even when branches are synchronized	Operation: Actual execution; Promotion Behavior: Forced CI/CD stress test
Test one repository first	Choose Safe Starter: Alloy Agent
Execute multiple known repositories without prompts	Use Selected repositories only and select the required repository cards
Execute every repository without prompts	Choose All repositories without prompt
Choose repositories in PowerShell at runtime	Choose Interactive repository prompt
Stop immediately after a problem	Enable Stop processing after the first failure
Capture logs in a dedicated folder	Enable Use custom transcript directory

7. Important Filename Note

# AnchorScript filename verified

Your command reference identifies the script as:

Invoke-ShelveraSequentialPromotionTest.ps1

However, the example commands in the same reference execute:

ts_git_commit_automation.ps1

The command builder defaults to the filename used by the runnable examples:

ts_git_commit_automation.ps1

Before running commands, verify the actual filename in your automation folder and update the Script File Name input at the top of this page when required.