Skip to content

Closes #106: Rewrite HOME.md and Setup.md for external customer-facing audience - #107

Merged
charlesgreen merged 1 commit into
mainfrom
sc/106
Aug 1, 2026
Merged

charlesgreen merged 1 commit into
mainfrom
sc/106

Conversation

@simplycubed-code

Copy link
Copy Markdown
Contributor

Automated change from an issue. A human reviews and merges; this loop does not.

Walkthrough

This change rewrites the repository's top-level product and setup documentation to speak to external customers rather than internal adopters. The README now presents SimplyCubed Code as a product teams install into their own GitHub, emphasizing customer control over repositories, runners, secrets, review, and merge decisions while explaining the issue-to-PR workflow in customer-facing language.

The setup guide is likewise reworked into a customer installation path. It walks a customer through installing the CLI, generating repo files, configuring the GitHub App and Azure credentials, running the one-time self-test, and operating the day-to-day issue and review loop, while removing the prior internal-project framing.

Changes

Area Summary
Product Overview Docs README.md reframes SimplyCubed Code as a customer-facing product overview, clarifies the deployment and trust model, and updates getting-started language around customer-owned GitHub workflows.
Customer Setup Guide docs/setup.md turns the adopter-oriented setup notes into a step-by-step customer install and usage guide covering prerequisites, app/secret setup, self-test, and normal issue-to-PR operation.

Generated description — verify against the diff.

🤖 Generated with SimplyCubed Code

…g audience

Co-Authored-By: SimplyCubed Code <noreply@simplycubed.com>
@codecov

codecov Bot commented Aug 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@charlesgreen
charlesgreen merged commit 6a57ebd into main Aug 1, 2026
3 checks passed
@charlesgreen
charlesgreen deleted the sc/106 branch August 1, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant