How to Contribute to an Existing Doc/Repository on GitLaw (Forking)

To contribute to an existing GitLaw repository, click Fork in the top-right corner of the repository to create your own copy, make your edits or add files in your fork, write a clear commit message, then click Contribute → Open Pull Request to submit your changes to the maintainers for review. Once approved, your changes are merged into the original.

Before you start: a GitLaw account.

How do I fork and contribute to a GitLaw repository?

GitLaw makes it easy to customise legal document templates for your own needs. Forking a repository creates your own version of an existing legal document collection, letting you tailor it while keeping it linked to the original. Contributing back improves templates for everyone:

1. Fork the repository: visit GitLaw's template library and search for the repository you would like to fork. Open the repository to review its contents, then click the Fork button in the top-right corner to create your own copy. This lets you make edits safely without affecting the original files.
2. Make changes: open your forked repository. For edits, click the file name to view its contents and select the Edit button to modify the file directly in the GitLaw editor. For new files, click Add File → Create New File, or upload an existing file with the appropriate formatting.
3. Write a clear commit message: describe the changes in the "Commit Message" field, for example "Updated confidentiality clause in NDA template to align with GDPR guidelines", and add any details about why the changes are valuable.
4. Submit a pull request: click Contribute → Open Pull Request in your forked repository. Add a title and description explaining what you have changed and why the changes are beneficial. Example title: "Updated GDPR Clause in NDA Template"; description: "Revised the confidentiality clause to ensure compliance with GDPR for businesses operating in the EU."
5. Collaborate on your contribution: the repository maintainers will review your pull request and may leave comments or suggestions. Address their feedback by making updates in your fork and pushing the changes.
6. Get your contribution merged: once approved, your changes are merged into the original repository, becoming part of the shared resource for all GitLaw users.

Why fork a repository?

A fork allows you to:

1. Create your own legal library: save a copy of a repository to your GitLaw account and modify it without affecting the original version.
2. Contribute to the community: suggest improvements or updates to the original repository by submitting pull requests with your changes.
3. Experiment safely: test edits and customisations in your forked repository without affecting others.

Why contribute to a repository?

1. Enhance existing resources: improve the quality and accuracy of legal documents.
2. Share your expertise: add your knowledge to the collective effort of the GitLaw community.
3. Collaborate with peers: work alongside other legal professionals and contributors.

Best practices for contributions

• Follow repository guidelines: check if the repository has a contribution guide.
• Be clear and precise: use clear language in your edits and commit messages.
• Keep edits focused: make one type of change per pull request for easier review.

Frequently asked questions

Does forking change the original repository?

No. A fork is your own copy, linked to the original. Your edits only affect the original if a maintainer approves and merges your pull request.

What happens after I open a pull request?

The repository maintainers review it and may leave comments or suggestions. Address their feedback in your fork, and once approved your changes are merged into the original repository.

Related articles

• How to add a new file to GitLaw
• How to publish a new contract template publicly on GitLaw

Reviewed by the GitLaw team. Last updated 29 July 2026.