Skip to content

Latest commit

 

History

History
72 lines (43 loc) · 3.18 KB

CONTRIBUTING.md

File metadata and controls

72 lines (43 loc) · 3.18 KB
Raw

Contribution Guidelines

Welcome to BitPost's contribution guidelines! We appreciate your interest in contributing to our AI-based Android app designed to generate engaging content for social media. Please review the following guidelines to ensure a smooth and effective collaboration.

Types of Contributions

We welcome contributions in the following areas:

  • Bug Fixes: If you encounter any issues or bugs in BitPost, please report them by creating a detailed bug report. Include information about the problem, steps to reproduce it, and details about your Android device.

  • Feature Additions: If you have ideas for new features or enhancements, feel free to share them. Provide detailed descriptions and use cases for better understanding.

  • Documentation Improvements: Help us enhance our documentation. Whether it's fixing a typo, adding examples, or creating new sections, every improvement is valuable.

  • Code Optimization: If you have suggestions for optimizing the existing codebase or improving performance, we're open to your insights.

Branch Naming Convention

When creating a new branch, please use the following prefixes to indicate the purpose of your contribution:

  • fix-issue--: For bug fixes and issue-related changes.

    • Example: fix-issue-123-fix-login-error

  • feature-: For adding new features or enhancements.

    • Example: feature-content-suggestions

  • docs-: For documentation-related changes.

    • Example: docs-update-user-guide

  • optimize-: For code optimization and performance improvements.

    • Example: optimize-content-generation

Coding Conventions

  • Follow the existing coding style and conventions used in the project.
  • Write clear, concise, and well-commented code.
  • Ensure your code is readable and maintainable.
  • Test your changes thoroughly before submitting a pull request.

How to Contribute

  1. Fork the Repository: Fork the BitPost repository to your GitHub account.

  2. Create a Branch: Create a new branch following the branch naming convention mentioned above.

    git checkout -b feature-content-suggestions

  3. Make Changes: Make your changes or additions in the newly created branch.

  4. Test Your Changes: Test your changes to ensure they work as expected and do not introduce any new issues.

  5. Commit Your Changes: Commit your changes with clear and descriptive commit messages.

    git commit -m "Add content suggestion feature"

  6. Push Your Changes: Push your changes to your forked repository on GitHub.

    git push origin feature-content-suggestions

  7. Open a Pull Request: Submit a pull request from your branch to the main BitPost repository. Provide a detailed description of your changes in the pull request.

Code Review Process

All submissions, including contributions by project members, are subject to code review. We appreciate your patience during this process and will work to get your changes merged as quickly as possible.

Thank you for considering contributing to BitPost! Your support helps make this app better for everyone.