GGlebux/QMS

Guide line for the collaboration or the repository

Ouverte

#1 ouverte le 14 sept. 2025

 (1 commentaire) (0 réaction) (0 personne assignée)Java (0 fork)auto 404
documentationgood first issue

Métriques du dépôt

Stars
 (0 étoile)
Métriques de merge PR
 (Aucune PR mergée en 30 j)

Description

1. Communicate.

You need to first communicate the issue or the feature that you believe it is missing, or you would like to work on. The communications need to take place in the Telegram group -> TECH room.

2. Create an issue or assign the issue to yourself ( if already created ).

The Issue creation is mandatory as it allows the team to keep track of the work that has been accomplished and share the approach. The description needs to mention the WHY and the HOW. Also, elaborate if possible to give clear guidance and steps.

3. Create a branch

Create a separate branch in which the feature or the troubleshooting will take place. The name needs to start with "fix" or "feature" to give further guidance.

Examples of branch naming: featute/edite-profile-details, fix/login-issue

4. Push the changes and make PR

Once the code is tested and pushed, open a Pull Request linked to the issue and invite your colleague to the review.

5. Important

Do not push your changes directly to the master branch

Guide contributeur