Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 2.63 KB

contributing.md

File metadata and controls

49 lines (35 loc) · 2.63 KB

Contributing

We welcome contribution, bug reports, fixes and suggestions from the community.

Branching guide

These branches are partially compliant to GitFlow branching model:

  • master - contains tagged release versions.
  • develop - contains in-development library state, used for feature-branching.
  • #version-branch - contains changes related to particular version development.
  • #issue-branch - contains changes related to particular issue.

The above nomenclature is followed for both umbrella-repository and single module repositories.

Issues

Preferred way to submit an issue is to submit that to the particular module you think the trouble is in. In case you are not sure, submit an issue to this (master) repository, so the development team could review the contents and create a necessary issues set in modules related.

Creating a discussion

Discussions should be created on GitHub for any proposed changes or suggestions to the library

Pull Requests

Pull request submission is complicated because of the suite is highly modular and particular changes are required to be pulled in convenient repository.

Depending on what you want to change, proceed your pull request to following repositories:

In case you are not sure which repository to proceed to, create an issue in this repository and ask.