Skip to content

Latest commit

 

History

History
58 lines (39 loc) · 2.51 KB

File metadata and controls

58 lines (39 loc) · 2.51 KB

Contributing to Learn PostgreSQL

Thank you for your interest in contributing to the Learn PostgreSQL project! Your help makes this resource better for everyone—whether by fixing typos, improving explanations, or adding new PostgreSQL tutorials.

Hacktoberfest 2025

This repository is open for Hacktoberfest 2025 contributions. Hacktoberfest is a month-long event in October that encourages participants to contribute to open-source projects. Completing four quality pull requests to participating repositories earns you a Hacktoberfest T-shirt or a tree planted in your name.

Learn more about Hacktoberfest here.

How to Contribute

  1. Fork the repository – Click the "Fork" button at the top right of this page.

  2. Clone your fork – Clone it to your local machine:

    git clone https://github.com/fahimahammed/learn-postgresql.git
  3. Create a branch – Make a new branch for your work:

    git checkout -b your-branch-name
  4. Make your changes – Fix typos, improve guides, or add new PostgreSQL content.

  5. Commit your changes – Write a clear and descriptive commit message:

    git add .
    git commit -m "Add guide for PostgreSQL JSON functions"
  6. Push your branch – Push your changes to your fork:

    git push origin your-branch-name
  7. Open a Pull Request – Go to the original repository and submit a PR with a detailed description of your changes.

Contribution Guidelines

  • New to open source? Start by reviewing issues and fixing small bugs, typos, or formatting errors.
  • Documentation – Keep language clear and concise. Improve readability wherever possible.
  • Code & Examples – Ensure your code is clean, follows best practices, and includes comments when necessary.
  • Community Standards – Be respectful, kind, and supportive in all interactions.

Issues

If you find a bug, have suggestions, or want to propose new content, feel free to create an issue with detailed information.

Review Process

  • Submitted PRs will be reviewed by maintainers.
  • Feedback may be provided, and updates requested to ensure quality.
  • Once approved, your PR will be merged into the main repository.

License

By contributing, you agree that your contributions will be licensed under the MIT License as detailed in the LICENSE file.