mirror of
https://github.com/documenso/documenso.git
synced 2025-11-10 04:22:32 +10:00
8367878395
## Description <!--- Describe the changes introduced by this pull request. --> <!--- Explain what problem it solves or what feature/fix it adds. --> ## Related Issue <!--- If this pull request is related to a specific issue, reference it here using #issue_number. --> <!--- For example, "Fixes #123" or "Addresses #456". --> ## Changes Made <!--- Provide a summary of the changes made in this pull request. --> <!--- Include any relevant technical details or architecture changes. --> - Change 1 - Change 2 - ... ## Testing Performed <!--- Describe the testing that you have performed to validate these changes. --> <!--- Include information about test cases, testing environments, and results. --> - Tested feature X in scenario Y. - Ran unit tests for component Z. - Tested on browsers A, B, and C. - ... ## Checklist <!--- Please check the boxes that apply to this pull request. --> <!--- You can add or remove items as needed. --> - [ ] I have tested these changes locally and they work as expected. - [ ] I have added/updated tests that prove the effectiveness of these changes. - [ ] I have updated the documentation to reflect these changes, if applicable. - [ ] I have followed the project's coding style guidelines. - [ ] I have addressed the code review feedback from the previous submission, if applicable. ## Additional Notes <!--- Provide any additional context or notes for the reviewers. --> <!--- This might include details about design decisions, potential concerns, or anything else relevant. --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Enhanced project README for clarity and improved environment variables section. - Added comprehensive developer and user documentation, including guides on local development, public API, self-hosting, and compliance standards. - Introduced specific guides for contributing, creating API keys, using webhooks, and setting up security measures. - Detailed documentation on various fields available for document signing to improve user understanding. - Added metadata structuring to improve navigation within the documentation site. - **Chores** - Updated `.gitignore` to better handle project files. - **New Features** - Introduced detailed metadata and documentation for various Documenso functionalities, including signing documents, user profiles, and compliance levels. - Added functionality for Direct Link Signing, enabling easy sharing for document signing. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Timur Ercan <timur.ercan31@gmail.com> Co-authored-by: Lucas Smith <me@lucasjamessmith.me> Co-authored-by: David Nguyen <davidngu28@gmail.com>
118 lines
3.9 KiB
Plaintext
118 lines
3.9 KiB
Plaintext
---
|
|
title: Contributing Guide
|
|
description: Learn how to contribute to Documenso and become part of our community.
|
|
---
|
|
|
|
import { Callout, Steps } from 'nextra/components';
|
|
|
|
# Contributing to Documenso
|
|
|
|
If you plan to contribute to Documenso, please take a moment to feel awesome. People like you are what open source is about. Any contributions, no matter how big or small, are highly appreciated.
|
|
|
|
This guide will help you get started with contributing to Documenso.
|
|
|
|
## Before Getting Started
|
|
|
|
<Steps>
|
|
|
|
### Check the Existing Issues and Pull Requests
|
|
|
|
Search the existing [issues](https://github.com/documenso/documenso/issues) to see if someone else reported the same issue. Or, check the [existing PRs](https://github.com/documenso/documenso/pulls) to see if someone else is already working on the same thing.
|
|
|
|
### Creating a New Issue
|
|
|
|
If there is no issue or PR for the problem you are facing, feel free to create a new issue. Make sure to provide as much detail as possible, including the steps to reproduce the issue.
|
|
|
|
### Picking an Existing Issue
|
|
|
|
If you pick an existing issue, take into consideration the discussion on the issue.
|
|
|
|
### Contributor License Agreement
|
|
|
|
Accept the [Contributor License Agreement](https://documen.so/cla) to ensure we can accept your contributions.
|
|
|
|
</Steps>
|
|
|
|
## Taking Issues
|
|
|
|
Before taking an issue, ensure that:
|
|
|
|
- The issue has been assigned the public label.
|
|
- The issue is clearly defined and understood.
|
|
- No one has been assigned to the issue.
|
|
- No one has expressed the intention to work on it.
|
|
|
|
After that:
|
|
|
|
1. Comment on the issue with your intention to work on it.
|
|
2. Start working on the issue.
|
|
|
|
Feel free to ask for help, clarification or guidance if needed. We are here to help you.
|
|
|
|
## Developing
|
|
|
|
The development branch is `main`, and all pull requests should be made against this branch. Here's how you can get started with developing:
|
|
|
|
<Steps>
|
|
|
|
### Set Up Documenso Locally
|
|
|
|
To set up your local environment, check out the [local development](/developers/local-development) guide.
|
|
|
|
### Pick a Task
|
|
|
|
Find an issue to work on or create a new one.
|
|
|
|
> Before working on an issue, ensure that no one else is working on it. If no one is assigned to the issue, you can pick it up by leaving a comment and asking to assign it to you.
|
|
|
|
Before creating a new issue, check the existing issues to see if someone else has already reported it.
|
|
|
|
### Create a New Branch
|
|
|
|
After you're assigned an issue, you can start working on it. Create a new branch for your feature or bug fix.
|
|
|
|
When creating a branch, make sure that the branch name:
|
|
|
|
- starts with the correct prefix: `feat/` for new features, `fix/` for bug fixes, etc.
|
|
- includes the issue ID you are working on (if applicable).
|
|
- is descriptive.
|
|
|
|
```sh
|
|
git checkout -b feat/issue-id-your-branch-name
|
|
|
|
## Example
|
|
git checkout -b feat/1234-add-share-button-to-articles
|
|
```
|
|
|
|
In the pull request description, include `references #yyyy` or `fixes #yyyy` to link it to the issue you are working on.
|
|
|
|
### Implement Your Changes
|
|
|
|
Start working on the issue you picked up and implement the changes. Make sure to test your changes locally and ensure that they work as expected.
|
|
|
|
### Open a Pull Request
|
|
|
|
After implementing your changes, open a pull request against the `main` branch.
|
|
|
|
</Steps>
|
|
|
|
<Callout type="info">
|
|
If you need help getting started, [join us on Discord](https://documen.so/discord).
|
|
</Callout>
|
|
|
|
## Building
|
|
|
|
Before pushing code or creating pull requests, please ensure you can successfully create a successful production build. You can build the project by running the following command in your terminal:
|
|
|
|
```bash
|
|
npm run build
|
|
```
|
|
|
|
Once the project builds successfully, you can push your code changes or create a pull request.
|
|
|
|
<Callout type="info">
|
|
Remember to run tests and perform any necessary checks before finalizing your changes. As a
|
|
result, we can collaborate more effectively and maintain a high standard of code quality in our
|
|
project.
|
|
</Callout>
|