microsoft / microsoft/react-native-gallery

Update contribution guide

Open
#440 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement
Dominant language
TypeScript
Stars
257
Forks
57
Avg merge
18h 19m
Merged PRs (30d)
10

Description

Current contribution guide is here: https://github.com/microsoft/react-native-gallery/wiki/Contributing-to-React-Native-Gallery
Mostly it covers pretty broad contribution topics, not the quirks specific to this repo. That's a fine doc to have... but we really need to capture what you need to know if you're going to work on this app.

Things like:

  • Running yarn test:update
  • Clearer callout of timeZoneOffsetInSeconds problem (it's a bit buried as is): https://github.com/microsoft/react-native-gallery/issues/441
  • Linting expectations (yarn lint clean)
  • Accessibility checking with Accessibility Insights 🧪
  • Anything else you might hit in the pipelines
  • Hotspots for manual testing
  • Platform-specific code
  • How to add a new sample page (note: covered in the readme)
  • App architecture overall

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing wiki contribution guide and the repository README, then review the listed workflows: yarn test:update, yarn lint, Accessibility Insights, manual testing hotspots, platform-specific code, and app architecture. Check issue #441 for the timeZoneOffsetInSeconds guidance. Done means the guide documents the repo-specific setup, checks, testing areas, sample-page guidance, and architecture without duplicating the README.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
accessibility, documentation, mobile-dev, testing-qa
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.