Pull Request Guidelines

[ANSHIKA-26]

Discussed in #99

^{Originally posted by ANSHIKA-26 October 2, 2024}
Pull Request Guidelines
To ensure smooth collaboration and maintain the quality of the project, please follow these guidelines when creating a Pull Request (PR).

1. Branching Strategy
   Always create a new branch for your PR and avoid working on the main or master branch directly.
   Use meaningful branch names that reflect the purpose of the changes (e.g., feature/add-authentication, bugfix/fix-login-issue).
2. Keep PRs Focused
   Make sure your PR addresses only one issue or feature at a time. Avoid combining unrelated changes in one PR.
   Keep the size of the PR manageable. Large PRs are difficult to review and may cause delays.
3. PR Checklist
   Before submitting a PR, ensure that:

You have synced your branch with the latest version of the main branch.
You have added necessary screenshots and videos to demonstrate the changes.
You have written or updated any necessary documentation (if applicable).
You have tested your changes to ensure they work as expected.

4. Descriptive Title and Message
   Use a clear and concise title for the PR that explains the change.
   In the PR description, provide:
   A brief explanation of the problem being solved or the feature being implemented.
   A list of changes made.
   References to any related issues (e.g., “Fixes Does not visible "Load More Post.." #123”).
   Any specific areas where the reviewer should focus.