Skip to content

Audit portfolio Pages use and stop commercial-hosting migrations #4300

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Objective

Decide which in-scope portfolio uses of GitHub Pages are suitable under current GitHub terms, stop the AS Coaching migration as directed, and create narrowly owned follow-ups for commercial or obsolete deployments. Part of #3896. This is a timeboxed policy/hosting spike, not authorization to remove a working site or a legal opinion from GitHub.

Maintainer direction — 18 October 2026

Stop migrating AS Coaching og Vaner to Pages and vet other portfolio Pages use. This supersedes the earlier static-sites-first hosting preference where it would move a commercial site onto unsupported hosting. Public source and free CI remain separate decisions.

Method and evidence

Read current official additional-product terms, Pages and Actions sections, live repository/Pages API state and actual public page purposes. Do not classify from repository visibility, a static adapter, a successful deployment, or a homepage metadata field alone.

Fresh census: 23 non-archived public organization repositories returned in a complete single page; five have Pages configured. The mapped private FleetDM product reports no Pages site. This is a bounded portfolio census, not a claim about every external client account, every historical URL or all hosting providers. Archived products and client-owned/employment repositories were not inspected.

Source owner Current observation, 18 October 2026 Decision / next action
business-site Pages is configured for devantler.tech; live page advertises priced development and hosting with customer enquiry paths. Choose the existing application-hosting path instead of relying on Pages for the business site; coordinate #3939 and business-site#102. Do not assert GitHub has adjudicated a violation, and preserve service until a verified cutover.
monorepo Its default Pages URL still returns HTTP 200 with the older business-site title, despite no current site/Pages publishing workflow and no Pages custom domain. Treat as a stale commercial-site copy, not a harmless disabled publisher. Create declarative safe retirement work, with current publisher/domain ownership and remaining dependencies checked first.
platform Default Pages endpoint returns HTTP 404 while Pages remains configured without a custom domain. Candidate stale configuration, not proof of a live commercial application. Resolve ownership and intended documentation use before retiring the setting; no need to migrate a nonexistent served site.
ksail Custom Pages domain serves KSail documentation and public project guidance. Retain as a project-documentation use on current evidence; prohibit assuming that a future paid platform/dashboard/service can use the same hosting entitlement. No blanket legal/OSS licence certificate.
data-product-controller / KHoist Custom Pages domain returns HTTP 200 and the KHoist documentation title. Retain project documentation; re-evaluate if it becomes hosted business/transactional functionality.
ascoachingogvaner No Pages site; no active Pages publisher or migration PR. Proposed issue #206 was Icebox. Cancel #206 as NOT_PLANNED under the maintainer's direction; keep existing hosting and its unrelated booking PR intact.

Decision

GitHub Pages is for the permitted project/showcase use, not our default free business-hosting product. Keep valid project documentation on it, cancel the AS Coaching proposal, plan the business-site move on the existing source-owned application path, and retire stale Pages publication through the configuration owner. A commercial mention alone is not an automatic breach; assess actual purpose and obtain GitHub clarification if material ambiguity remains before relying on the service.

Do not activate a portal, change DNS, delete Pages, disable CI/security, change a licence, inspect a client-owned repo or contact GitHub as part of recording this decision. Code can remain public with appropriate authorization even when the deployed site uses another host.

Acceptance Criteria

  • Record the dated scoped census, actual site purposes, decisions, uncertainties and current official terms; avoid declaring all public/static/commercially licensed projects equivalent.
  • Verify AS Coaching chore(deps): Bump projects/dotnet-commons from 2ead0b1 to 9395afa #206 is cancelled as not planned and no migration publisher/PR is left to continue it.
  • Link the existing business-site deployment work, with a public-site-only cutover path considered separately from portal login/payment activation. Keep current service until replacement and rollback proof exist.
  • File safe retirement of the stale monorepo copy and resolve the platform Pages setting through .github's declarative owner, not imperative configuration changes.
  • Add a prospective Pages-purpose/terms review to repository onboarding so the rejected technical-only assumption does not recur. Connect it with the client-controlled source/cost epic and monorepo#4247's supplier assessment.
  • Publish only the sanitized decision and follow-ups, then close this Spike. Do not pretend that recording them has completed any hosting migration or proved legal compliance.

Priority High, effort Low for this decision/follow-up spike, service class Risk reduction. Hosting implementation and live cutover effort remain in their separately estimated delivery issues.

Activity

  1. self-assigned this
    on Oct 18, 2026
  2. added theissue type on Oct 18, 2026
  3. moved this to 📥 Backlog in 🌊 Project Boardon Oct 18, 2026
  4. updated Priority High and Effort Low on Oct 18, 2026
  5. devantler commented on Oct 18, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Decision and follow-ups recorded

    The bounded portfolio Pages review in this Spike is complete. Live API settings and public responses—not a static-build assumption—support the decision table in the body. The 23 active public repositories yielded five configured Pages sites; the mapped private FleetDM product has none. The current scope deliberately excludes external client/employment repositories and does not claim an exhaustive historical-domain or provider-account audit.

    • AS Coaching #206 is readback-verified CLOSED / NOT_PLANNED. There was no Pages site, active Pages publisher or migration PR. Its unrelated booking PR and current hosting were left untouched.
    • monorepo#3939 retains the unified source-owned application-hosting path. A new policy note makes the business-site move explicit and asks refinement of a public-site-only cutover without activating unverified private portal features. Replacement, DNS/certificate, rollback and actual visitor proof remain mandatory before retiring current service.
    • .github#638 records the confirmed HTTP-200 older monorepo business-site copy and the separately classified platform HTTP-404 setting. It must prove ownership and purpose, then safely retire only what is obsolete through the reviewed configuration path. Neither has been deleted by this Spike.
    • .github#639 will enforce prospective repository-profile/hosting-purpose admission and funding checks. business-site#177 links the public/private source and tenant choices, which do not depend on using Pages.
    • Project documentation at KSail and KHoist stays on Pages on current purpose evidence. There is no blanket assertion that every commercial mention is disallowed, every repository is open source, or future commercial runtime functionality is permitted there.

    This completes the Spike's research decision and filed follow-ups only. Implementation, Pages retirement, the business-site move, individual client permissions, account entitlements and legal compliance are not marked delivered. Close the Spike as completed; the separately boarded delivery issues remain open.

  6. moved this from 📥 Backlog to ✅ Done in 🌊 Project Boardon Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

High

Effort

Low

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions