Contribuyendo a SubQuery

¡Bienvenido y un gran agradecimiento por considerar contribuir a este proyecto de SubQuery! Juntos podemos allanar el camino hacia un futuro más descentralizado.

Note This documentation is actively maintained by the SubQuery team. We welcome your contributions. You can do so by forking our GitHub project and making changes to all the documentation markdown files under the `docs` directory. :::

What follows is a set of guidelines (not rules) for contributing to SubQuery. Following these guidelines will help us make the contribution process easy and effective for everyone involved. It also communicates that you agree to respect the time of the developers managing and developing this project. In return, we will reciprocate that respect by addressing your issue, considering changes, collaborating on improvements, and helping you finalise your pull requests.

Código de Conducta

We take our open source community projects and responsibility seriously and hold ourselves and other contributors to high standards of communication. By participating and contributing to this project, you agree to uphold our Code of Conduct.

Primeros pasos

Contributions to our repositories are made through Issues and Pull Requests (PRs). A few general guidelines that cover both:

• Busca problemas y PRs existentes antes de crear los tuyos.
• Trabajamos arduamente para garantizar que las cuestiones se traten con rapidez, pero dependiendo del impacto, podría tardar un tiempo en investigar la causa raíz. Una mención amigable @ en el hilo de comentarios para el envío o un colaborador puede ayudar a llamar la atención si su problema está bloqueando.

¿Cómo contribuir?

Informar de fallos

Bugs are tracked as GitHub issues. When logging an issue, explain the problem and include additional details to help maintainers reproduce the problem:

• Utilice un título claro y descriptivo para identificar el problema.
• Describa los pasos exactos para reproducir el problema.
• Describa el comportamiento que observó después de seguir los pasos.
• Explicar qué comportamiento esperabas ver en su lugar y por qué.
• Incluye capturas de pantalla si es posible.

Envío de Pull Request

In general, we follow the "fork-and-pull" Git workflow:

• Fork the repository to your own Github account.
• Clone the project to your machine.
• Create a branch locally with a succinct but descriptive name.
• Commit changes to the branch.
• Following any formatting and testing guidelines specific to this repo.
• Push changes to your fork.
• Open a PR in our repository.

Convenciones de Código

Mensajes de Git Commit

• Use the present tense ("Add feature" not "Added feature").
• Use the imperative mood ("Move cursor to..." not "Moves cursor to...").
• Limit the first line to 72 characters or less.

Guía de estilo de JavaScript

• All JavaScript code is linted with Prettier and ESLint.