Submit a pull request on github
Fork a GitHub repository with adult guidance, make a small change to a file, commit it, and submit a pull request explaining the change.
About this activity
Fork a GitHub repository with adult guidance, make a small change to a file, commit it, and submit a pull request explaining the change.
What you need
Step by step
- 1
Step 1
Ask an adult to help you sign in to your GitHub account in a web browser.
- 2
Step 2
Ask the adult to open the repository link on GitHub or type the link into the browser address bar.
- 3
Step 3
Click the "Fork" button at the top-right of the repository page to copy the project into your account.
- 4
Step 4
Wait for GitHub to finish forking and then open the forked repository in your account.
- 5
Step 5
Click the file you want to change so it opens in the file view.
- 6
Step 6
Click the pencil icon (Edit file) to open the web editor for that file.
- 7
Step 7
Make one small change in the file such as fixing a typo or adding one clear sentence.
- 8
Step 8
In the "Commit changes" box type a short commit message that explains your single change.
- 9
Step 9
Click the "Commit changes" button to save your edit to your fork.
- 10
Step 10
Click the "Compare & pull request" button and write a simple description that explains what you changed and why.
- 11
Step 11
Click "Create pull request" to submit your change for review and then share your finished creation on DIY.org.
Fun facts
How do I help my child submit a pull request on GitHub?
Start by forking the repository on GitHub (click Fork). With an adult, open the fork in the browser and use the web editor or clone the repo locally. Make one small change to a file (like fixing a typo in README), write a clear commit message, and save to a new branch. Push the branch if working locally, then click New Pull Request, add a short description explaining the change, and submit. Have an adult review and help finalize the PR.
What materials do I need to submit a pull request with my child?
You’ll need a computer or tablet with internet access and the repository URL. Create a GitHub account with parental permission (or use a parent-managed account). Optionally install Git and a text editor for local editing, though GitHub’s web editor works well for simple changes. Have a parent present to supervise account setup, review edits, and help with commits. Prepare a simple task, like correcting a typo or adding one sentence, so the child can safely contribute.
What ages is submitting a pull request suitable for?
This activity fits children about 8+ for guided, web-based edits when an adult helps. Kids aged 12+ can learn local Git workflows, branching, and commits with some independence. For younger children (5–7), try a simplified version where the adult performs clicks while the child suggests content, or practice editing plain text first. Adjust the complexity to the child’s reading, typing, and attention skills, and always provide adult supervision for account and privacy safety.
What are the benefits and safety tips for kids submitting pull requests?
Making pull requests teaches clear communication, collaboration, and basic version control—valuable digital skills and confidence in contributing. For safety, use a parent-supervised or child-friendly GitHub account, avoid sharing personal information in profiles or commits, and review contribution guidelines together. Start with low-risk edits, check changes before submitting, and discuss online etiquette. Adult oversight ensures privacy and helps the child learn responsible, positive participa
Watch & Learn
Need help?
What can we use instead if we don't have a computer or our own GitHub account?
If you don't have a personal GitHub account or a computer, use a parent's or teacher's supervised account or a tablet/phone browser to open the repository link, click Fork, and use the web editor (pencil icon) to make your change.
The Fork or pencil icon isn't working — what should we try next?
If the Fork button or pencil icon won't work, first confirm you are signed in with the adult (step 1) and viewing your forked repository (your username in the URL), then refresh the page or try a different browser.
How can we adapt the steps for different ages?
For younger children, have the adult handle signing in and clicking Fork while the child chooses a simple typo fix in the README and dictates the short commit message, and for older kids let them edit files in the web editor, write a descriptive commit message, and submit the Compare & pull request themselves.
How can we extend or personalize this pull request activity after completing the steps?
To enhance the activity, personalize your contribution by editing the project README to add one photo or one sentence about yourself, then add a clear commit message and update the pull request description to explain the outcome before sharing on DIY.org.