# Forks, clones and remotes — Open Source Contribution Guide

Source: https://www.geekswithgeeks.com/en/open-source/open-source-06

> Use Forks, clones and remotes to make a clear, evidence-based decision.

## Understand Forks, clones and remotes

Start by naming the decision behind **Forks, clones and remotes**. A strong answer explains the goal, the constraints, and the evidence you would use before acting. Do not treat a checklist as understanding: connect each step to the outcome it protects.

## Keep the workflow visible

Use this simple path while practising **Forks, clones and remotes**: understand the situation, make one deliberate choice, then review the result.

![A four-stage workflow for Forks, clones and remotes.](assets/figures/open-source/section-2-map.svg) — Figure 2.1 — Decide, act, check and improve.

## A useful comparison

Think of **Forks, clones and remotes** like planning a journey: a destination without a route is only a wish, while a route without a destination wastes effort.

Check the decision, not just the terminology.

**Quiz:** What is the most useful way to apply Forks, clones and remotes?

- [x] State the goal, constraints and evidence before choosing an action.
- [ ] Copy a template without checking whether it fits.
- [ ] Use the most complex option first.

*Answer:* State the goal, constraints and evidence before choosing an action.. Good practice makes the reasoning visible, so you can review and improve it.
