Skip to content

Latest commit

 

History

History
88 lines (61 loc) · 3.74 KB

CONTRIBUTING.md

File metadata and controls

88 lines (61 loc) · 3.74 KB
Raw

Contributing instructions

Thank you for considering to contribute to the Taiga INPS Bug Tracking repository! Here you will find instructions and guidelines for contributing efficiently.

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Issues

If you find an issue in the website or in this repository, please check if it's already known by searching the issue section, otherwise file a new one: we really appreciate it! 🚀.

You're welcome to contribute to open issues with more information or by adding :+1: on them: it will help the maintainers identify the issues to be prioritized.

Creating a new issue

There are three templates for new issues: Bug report, Feature request and General issue, pick the relevant one and follow the instructions in that template.

If you pick General issue please provide a good amount of detail in order to let other people clearly understand the issue. After the creation of the issue, the maintainers team will promptly triage it by assigning the proper labels.

Pull Requests

After opening an issue, you may want to further contribute. That's great and always appreciated! 😎

ℹ️ Please ensure that there is a pertinent issue related to what you are proposing and also make sure that someone has already reviewed it before proceeding

  1. Fork the project

  2. Follow our conventions regarding commits for your commit message

  3. Open a Pull request against dev. Blank PRs have a template you can follow where you can tick a checklist. When each one of the step is done, please insert an x in between the [ ] to mark it as ready.

ℹ️ Please make sure that all the relevant tests have been run and the CI processes triggered by the commits in the PR are passing without failures. If this is not the case, the PR will not be reviewed so you have to fix them before requesting help

Commit messages

The commit message should be simple and self-explanatory.

We follow the Conventional Commits format and the general rules of great commit messages (read this!)

If a commit fixes an issue, please reference it in the commit body with Fix: #ISSUENUMBER.

Gitflow

This repository adopts a simplified branch management system as follows:

  • main is stable and gets deployed automatically. Never push directly to it;
  • dev is the development branch and should be considered unstable;
  • feature or fix branches are derived directly from dev.

Releases

Please check the Releases page to see the current and past releases.

To see which are the next ones, please check our Milestones.

The maintainers try to keep the milestones updated in order to show what will be fixed soon and, when possible, they also try to set a consistent end date for such a milestone to be hit.