Issues and pull requests
Discuss a design and review changes before merging.
Track work with issues
Use the Issues tab to report a problem, propose an improvement, or ask a design question. Include the revision, affected Thing or file, and steps to reproduce where relevant. Comments support replies and reactions.
Open a pull request
Make changes on a branch, then use Pull requests → New pull request to choose the source and target branches. Explain the physical change and why it is needed, including any manufacturing or compatibility impact.
Review in four tabs
Conversation collects discussion and commit activity. Commits lists the commits in the request. Things changed groups changes around physical objects. Files changed focuses on modified repository files rather than repeating unchanged files.
Understand hardware diffs
Supported artifacts can show visual model, schematic, or Gerber comparisons, BOM redlines, and extracted parametric changes. Coverage depends on the file format and extracted data. Review the original files when a visual or structured diff is unavailable.
Discuss and merge
Reply to a specific comment or the main description, use reactions for lightweight feedback, and hover a reaction to see its participants. Resolve review questions before merging; merge controls depend on your project permissions and branch state.