Skip to content

docs: add prerequisites and setup instructions to Contributing section - #13

Open
myakura wants to merge 4 commits into
textlint:mainfrom
myakura:improve-contributing-docs
Open

docs: add prerequisites and setup instructions to Contributing section#13
myakura wants to merge 4 commits into
textlint:mainfrom
myakura:improve-contributing-docs

Conversation

@myakura

@myakura myakura commented Mar 16, 2026

Copy link
Copy Markdown
Contributor

Summary

The Contributing section only had a generic GitHub workflow with no mention of required tools. As a new contributor, I spent a few minutes trying to figure out which tools to install and what versions were expected — none of that was documented.

This PR adds:

  • Prerequisites — Node.js and Bun with versions taken from .tool-versions
  • Setupbun install to get started
  • Commands — the key scripts a contributor would need (bun test, bun run build, bun run tsc, bun run ci)

🤖 Generated with Claude Code

myakura and others added 3 commits March 17, 2026 03:31
The contributing section only had a generic GitHub workflow with no
mention of required tools or how to set up the project. New contributors
had to spend time figuring out that Bun (and Node.js for npm publishing)
are needed, and which versions to install. Added prerequisites with
versions from .tool-versions, setup command, and key development commands.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates the README’s Contributing section to better onboard new contributors by documenting required tooling and common development commands.

Changes:

  • Added prerequisites (Node.js + Bun) and pointed to .tool-versions for pinned versions.
  • Added basic setup instructions (bun install).
  • Documented key contributor commands (test/build/typecheck/CI).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md Outdated
Comment thread README.md
### Commands

```sh
bun test # run tests

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

i'm planning to drop vitest dependency for bun:test in #12 so let's just wait a bit see if it's accepted.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@myakura

myakura commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

Hi @3w36zj6, just a gentle follow-up — whenever you have a moment, could you please take a look at this PR? I've also opened #12 and, more recently, #20 if you're able to review those as well. No rush at all, thank you for maintaining this project!

@3w36zj6

3w36zj6 commented Aug 10, 2026

Copy link
Copy Markdown
Member

I agree that the existing contributing guide is rather sparse. However, the required tools, package manager, and available tasks are already clear from .tool-versions, package.json, and bun.lock. Repeating that information here feels redundant and creates another place that could drift out of sync over time.

I think contributor documentation is most valuable when it captures project-specific knowledge that cannot be inferred from the codebase itself.

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.

3 participants