‍GitLaw makes it easy for you to customize legal document templates for your own needs. Forking a repository is the first step to create your own version of an existing legal document collection, allowing you to tailor it while keeping it linked to the original repository.

Contributing to an existing GitLaw repository helps improve legal templates and ensures they remain accurate and useful for everyone. Whether you're updating a clause, fixing an error, or adding a new template to an established collection, your input makes a difference. Here’s a step-by-step guide to contributing to a repository on GitLaw.

‍

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 customizations in your forked repository without affecting others.

‍

Why Contribute to a Repository?

Contributing allows you to:

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.

‍

Steps to Contribute

‍

Step 1: Fork the Repository

1. Visit GitLaw’s Repository Library and search for the legal document repository you’d like to fork (e.g., "UK Employment Documents ").
2. Open the repository to review its contents and ensure it fits your needs.
3. Click the Fork button in the top-right corner to create your own copy of the repository.

This lets you make edits safely without affecting the original files.

‍

Step 2: Make Changes

1. Open your forked repository on GitLaw.
2. Locate the file you want to edit, or add a new file to enhance the repository.

For Edits:

• Click the file name to view its contents.
• 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.

‍

Step 3: Write a Clear Commit Message

1. Describe the changes you made in the "Commit Message" field.
   • Example: “Updated confidentiality clause in NDA template to align with GDPR guidelines.”
2. Provide any necessary details about why the changes are valuable.

‍

Step 4: Submit a Pull Request

1. After making your changes, click Contribute > Open Pull Request in your forked repository.
2. Add a title and description for your pull request to explain:
   • What you’ve changed.
   • 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.

‍

Step 5: Collaborate on Your Contribution

1. The repository maintainers will review your pull request and may leave comments or suggestions.
2. Address their feedback by making updates in your fork and pushing the changes.

Step 6: Get Your Contribution Merged

Once approved, your changes will be merged into the original repository, becoming part of the shared resource for all GitLaw users.

‍

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.

‍

Start Contributing Today

GitLaw thrives on collaboration. By contributing to an existing repository, you help create a more comprehensive and reliable resource for the entire legal community. Find a repository you’re passionate about, and start making a difference today!