Skip to content

Latest commit

 

History

History
56 lines (36 loc) · 1.77 KB

CONTRIBUTING.md

File metadata and controls

56 lines (36 loc) · 1.77 KB

Contributing to HybridTestFramework

We appreciate your interest in contributing! Whether you’re filing a bug report, proposing a new feature, or improving our documentation, every contribution makes a difference.

Getting Started

  1. Review our README for project details.
  2. Check out our Code of Conduct to understand the standards we preserve.

Bug Reports

  • Provide clear steps to reproduce the issue.
  • Detail the expected vs. actual outcome.
  • If the bug is not reproducible, the issue may be closed.

Feature Requests

  • Create an issue describing your proposed feature or improvement.
  • Outline why it benefits the project and how you envision using it.

Pull Requests

  • Fork the repository and create a new branch for your changes.
  • Include relevant tests where applicable.
  • Document your changes in the PR description.
  • Ensure the PR references any related issues.

Code Optimization

  • If you see opportunities to optimize the code (performance, readability, or structure), feel free to open a PR.
  • Explain the rationale behind your improvements and how they benefit the project.

Additional Guidelines

  • Respect our Code of Conduct.
  • Make sure to run or update tests before submitting.
  • For major changes, discuss via an issue first to avoid rework.

Development Setup

  • Clone the repository and install dependencies.
  • Run tests locally to confirm everything works.
  • Follow any local environment configuration specified in the README.

Commit Message Guidelines

  • Use clear, descriptive messages.
  • Reference related issues (e.g., “Fix #123: Resolve login errors”).
  • Keep commits focused on a single change to ease review.

Thank you for helping the HybridTestFramework grow and improve!