Skip to content

Simplify the onboarding company name label - #11080

Open
scotttong wants to merge 2 commits into
masterfrom
fix/onboarding-name-label
Open

Simplify the onboarding company name label#11080
scotttong wants to merge 2 commits into
masterfrom
fix/onboarding-name-label

Conversation

@scotttong

@scotttong scotttong commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Thinking Path

  • Paperclip is the open source app people use to manage AI agents for work
  • The onboarding wizard helps a user create the first company
  • The first form currently labels the company field as "Company name"
  • The surrounding context already makes the field purpose clear
  • A shorter label reduces repeated wording on the first screen
  • This pull request changes the field label to "Name"
  • The benefit is a simpler and more direct onboarding form

Linked Issues or Issue Description

What existing behavior does this improve?

The first screen of the onboarding wizard uses a longer label for the company name field.

Subsystem affected

ui/ — React and Vite board UI.

Current behavior

The field label reads "Company name".

Proposed behavior

The field label reads "Name".

Reason and benefit

The screen already provides company context. The shorter label removes repeated wording and keeps the form concise.

Breaking changes

None. This change only updates visible copy.

The GitHub search found no duplicate or closely related open issue or pull request.

What Changed

  • Changed the first onboarding company field label from "Company name" to "Name".
  • Added a focused regression test for the exact field label.

Verification

  • pnpm check:token-gates — all three token gates are clean.
  • pnpm typecheck — passed for all workspace packages.
  • pnpm --filter @paperclipai/ui exec vitest run src/components/OnboardingWizard.test.tsx — 1 test passed.
  • Open the first onboarding screen and confirm that the company field label reads "Name".
  • Snapshot baselines were intentionally not updated. The decision sheet marks per-change snapshot verification as dormant in "Per-change snapshot verification demoted to dormant (Jul 13 2026)".

Risks

  • Low risk. The change only updates one visible label and does not change form state or submission behavior.

For core feature work, check ROADMAP.md first and discuss it in #dev before opening the PR. Feature PRs that overlap with planned core work may need to be redirected — check the roadmap first. See CONTRIBUTING.md.

Model Used

  • OpenAI Codex with GPT-5. The context window size is not exposed. Agentic reasoning and tool use were enabled.

Checklist

  • I have included a thinking path that traces from project context to this change
  • I have specified the model used (with version and capability details)
  • I have checked ROADMAP.md and confirmed this PR does not duplicate planned core work
  • I have searched GitHub for duplicate or related PRs and linked them above
  • I have either (a) linked existing issues with Fixes: # / Closes # / Refs # OR (b) described the issue in-PR following the relevant issue template
  • I have not referenced internal/instance-local Paperclip issues or links (only public GitHub #NNN / github.com/paperclipai/paperclip URLs)
  • My branch name describes the change (e.g. docs/..., fix/...) and contains no internal Paperclip ticket id or instance-derived details
  • I have run tests locally and they pass
  • I have added or updated tests where applicable
  • I have updated relevant documentation to reflect my changes
  • I have considered and documented any risks above
  • All Paperclip CI gates are green
  • Greptile is 5/5 with no open P2s, recommendations, or follow-ups
  • I will address all Greptile and reviewer comments before requesting merge

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@commitperclip

commitperclip Bot commented Aug 8, 2026

Copy link
Copy Markdown

✅ All checks passing — ready for Greptile review and maintainer approval.

— commitperclip

@greptile-apps

greptile-apps Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR simplifies the first onboarding company-field label from “Company name” to “Name” and adds a focused assertion for the new copy.

  • Introduces a shared constant for the concise label.
  • Uses that constant in the onboarding form.
  • Adds a Vitest regression test for its exact value.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename Overview
ui/src/components/OnboardingWizard.tsx Replaces the onboarding company-name label with a shared constant containing “Name”; no eligible follow-up issue was identified.
ui/src/components/OnboardingWizard.test.tsx Adds a focused test asserting the new label constant; no eligible follow-up issue was identified.

Reviews (2): Last reviewed commit: "test: cover onboarding company name labe..." | Re-trigger Greptile

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@scotttong
scotttong marked this pull request as ready for review August 8, 2026 03:04
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