Publish Strategy to GitHub

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

1. Publishing commands

Publication uses the bundled GitHub extension. If sign-in is needed, authorize the intended account and check write access to the destination. A second publication cannot run concurrently.

Application screenshotXTester 1.0.0-preview.1

Enlarge screenshot

1. GitHub sign-in prompt

A strategy needs a persistent identity. If asked to open it in Studio first, do so and restart preparation rather than inventing an identifier to bypass the check.

Choose a new or existing repository. For a new one supply its name and visibility. For an existing repository, select it or enter owner/repository; write access is required.

Choose a publication directory in an existing repository. An empty value means its root; a subfolder such as strategies/FirstCheck makes the destination explicit.

Visibility belongs to the whole repository. Changing an existing destination between Public and Private affects its other files and history, requires suitable permission and is disclosed before confirmation.

A text preview and a separate confirmation precede publication. They show strategy/file counts, directory, visibility, conflicting files to replace and previously published files to remove.

The snapshot is bound to current files and project. Changes to source, selected project or remote repository during preparation cause rejection. Restart and review the new snapshot; previous confirmation does not cover new contents.

Data, logs, results and common secret files are excluded from collection. Still inspect your source files for content you did not intend to publish.

This publishes a strategy source snapshot or portfolio composition with participant bindings. It does not launch a robot, install dependencies or release XTester. It does not create a nested Git repository in the source folder.

Price history, results, compiled DLL/EXE files and excluded artifacts do not form a portable runtime package. On another machine, separately check version, dependencies, data and run configuration.

Success establishes writing the snapshot to GitHub, not successful compilation or strategy quality. Open the resulting link and compare destination and files with the reviewed preview.

Use Own Launcher (White Label)… to distribute a complete robot application with its name and logo. Publishing source to GitHub and packaging that application serve different purposes.

Access failure: check the active GitHub account, write permission and enabled bundled GitHub extension. Archived, disabled or unsupported repository types cannot be used as an ordinary destination.

Changed project: save source and prepare a new snapshot rather than confirming an old preview. External symbolic links and invalid paths cannot collect files outside the selected root.

Snapshots are limited to 1000 files and 20 MiB. Separate intended source from excess artifacts and review again when over the limit. For another failure retain the exact message and destination, without access tokens.