Skip to content

📖 docs(contributing): expand CONTRIBUTING.md with full local dev and workflow guide#650

Open
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
docs/contributing-guide
Open

📖 docs(contributing): expand CONTRIBUTING.md with full local dev and workflow guide#650
kubestellar-hive[bot] wants to merge 1 commit into
mainfrom
docs/contributing-guide

Conversation

@kubestellar-hive
Copy link
Copy Markdown
Contributor

@kubestellar-hive kubestellar-hive Bot commented May 27, 2026

Summary

Replaces the 4-line CONTRIBUTING.md stub (bead 27949a40) with a full contributor guide.

Changes

  • Prerequisites table (Node.js 18+, npm, optional just)
  • Local development setup steps (clone → install → dev server)
  • Repository structure section with component map (bluespeed/, dakota/, knuckle/)
  • Code style / ESLint formatting guidance
  • PR workflow with DCO sign-off instructions (git commit -s)
  • Conventional commit examples
  • Retains pointer to docs site and OS-image repos

Why

The old CONTRIBUTING.md read: "Thank you for contributing. See docs.projectbluefin.io/contributing." It did not describe the actual Vite+Vue+Tailwind stack or the repo structure. New contributors had no local dev path without reverse-engineering the justfile and package.json.
Refs #648

- Add prerequisites table (Node.js 18+, npm, optional just)
- Add local development setup steps
- Add repository structure section with component map
- Add code style / ESLint formatting guidance
- Add PR workflow with DCO sign-off instructions
- Add conventional commit examples
- Retain pointer to docs site and OS-image repos

Addresses: guide bead 27949a40 — CONTRIBUTING.md was a 4-line stub
that redirected away without any website-specific contributor info.

Signed-off-by: ci-maintainer <ci-maintainer@projectbluefin.hive>
@kubestellar-hive kubestellar-hive Bot added the ready-for-review CI green, ready for human review label May 27, 2026
Copy link
Copy Markdown
Member

@hanthor hanthor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR has merge conflicts with main branch. Please resolve CONTRIBUTING.md conflicts and re-sync with base branch, then we can approve.

Copy link
Copy Markdown
Member

@hanthor hanthor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good expansion of the CONTRIBUTING.md with concrete steps for first-timers. The fork/clone/branch workflow section was clearly missing. Approved.

Copy link
Copy Markdown
Member

@hanthor hanthor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

Changes: 1 file, CONTRIBUTING.md (+194/-4). Replaces the 4-line stub with a comprehensive contributor guide.

Content quality ✅

  • ✅ Clear prerequisites table (Node.js 18+, npm, optional

project-bluefin-website@0.1.0 build
vue-tsc && vite build)

  • ✅ Step-by-step local dev setup (clone → install → dev server)
  • ✅ Comprehensive repo structure map with component directories
  • ✅ Code style/ESLint guidance consistent with project config
  • ✅ Conventional commit examples match project conventions
  • ✅ DCO sign-off instructions (On branch resolve-contributing-conflicts
    nothing to commit, working tree clean) clear and correct
  • ✅ Points to TRANSLATION-GUIDE.md for i18n workflow

Structural note ⚠️

  • This PR has merge conflicts with main (tracked as #654). PR #657 resolves these conflicts by keeping this branch's content. Once #657 is merged/cherry-picked, this PR's conflicts will be resolved.

Verdict

Well-structured, accurate, comprehensive. LGTM pending conflict resolution.

Copy link
Copy Markdown
Member

@hanthor hanthor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

Changes: 1 file, CONTRIBUTING.md. Replaces 4-line stub with comprehensive guide.

Content quality: prerequisites, local dev setup, repo structure, code style, conventional commits, DCO sign-off all correct and well-structured. Points to TRANSLATION-GUIDE.md.

Note: Has merge conflicts (tracked as #654, PR #657 resolves). LGTM pending resolution.

Copy link
Copy Markdown
Member

@hanthor hanthor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed — comprehensive CONTRIBUTING.md expansion with dev workflow. LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-review CI green, ready for human review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant