Skip to content

docs: improve contributor experience with setup guide and enhanced gitignore #39247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

surajsk2003
Copy link

Why

Improve the onboarding experience for new contributors by providing clear setup instructions and better project hygiene.


What's Being Changed

Enhanced README.md

  • Added Prerequisites section with Node.js version requirements
  • Added Quick Start section with step-by-step installation instructions
  • Added Available Scripts section explaining common npm commands

Improved .gitignore

  • Included a comprehensive list of common files and directories to ignore
  • Added OS-specific files (.DS_Store, Thumbs.db, etc.)
  • Ignored build artifacts and cache directories

Created CONTRIBUTING.md

  • Included a simple setup guide for new contributors
  • Added suggestions for easy first contributions
  • Linked to detailed documentation and community guidelines

Checklist

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR
    In most cases, the author can be the SME. For open source contributions, GitHub staff may review.
  • The changes in this PR meet the Docs content fundamentals.
  • All CI checks are passing and the changes look good in the review environment.

Let me know if any adjustments are required. Happy to improve the experience for future contributors!

@Copilot Copilot AI review requested due to automatic review settings July 10, 2025 01:20
Copy link

welcome bot commented Jul 10, 2025

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 10, 2025
Copy link
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

This pull request contains code changes, so we will not generate a table of review links.

🤖 This comment is automatically generated.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR improves the onboarding experience by enhancing the main README with clear setup instructions and introducing a dedicated CONTRIBUTING guide.

  • Expanded README with prerequisites, quick start steps, and script explanations
  • Added a CONTRIBUTING.md with first-time setup, branch workflow, and easy-entry tasks

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File Description
README.md Added Prerequisites, Quick Start, and Available Scripts sections
CONTRIBUTING.md New contributor guide covering setup, change workflow, and help resources
Comments suppressed due to low confidence (4)

README.md:10

  • Use an asterisk (*) instead of a hyphen for bullet lists to comply with the repository's Markdown style guidelines.
- **Node.js**: Version 20 or 22 (see [engines](package.json) in package.json)

README.md:37

  • Switch this list item to use an asterisk (*) instead of a hyphen for consistency with the project content guidelines.
- `npm run dev` - Start development server with English content only

CONTRIBUTING.md:1

  • Replace the hardcoded product name “GitHub Docs” with the corresponding Liquid variable (e.g. {% data variables.product.github %}) to ensure variable-driven consistency across content.
# Contributing to GitHub Docs

CONTRIBUTING.md:54

  • Use an asterisk (*) for this bullet list item instead of a hyphen to align with the Markdown bulleted list convention in our content guidelines.
- Fix typos in documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Do not begin working on this issue until triaged by the team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant