Skip to content

Latest commit

 

History

History
27 lines (17 loc) · 1.23 KB

File metadata and controls

27 lines (17 loc) · 1.23 KB

If you feel that any customisations are useful to the Amplience ecosystem, we welcome contribution. These can range from your own integrations, new capabilities or just typos and bug fixes.

Instructions

Forking

These steps will guide you through contributing to this project:

  • Fork the repo
  • Clone it and install dependencies

Committing

Make and commit your changes. Make sure the commands npm run build and npm run test:prod are working.

When committing changes, it is useful to follow a standard practice for readability. We would reccomend following Conventional Commits

Documentation

Please do not forget to add documentation for other users in markdown format as part of your pull request

Pull Requests

Finally send a GitHub Pull Request with a clear list of what you've done.

Make sure all of your commits are atomic (one feature per commit).

Process

If Amplience can understand, review the changes and feel they are stable and add value to all, we will merge the pull request into this project.

Note: There are no SLA's for PR's