Skip to content
This repository has been archived by the owner on May 15, 2024. It is now read-only.

Latest commit

 

History

History
118 lines (67 loc) · 3.57 KB

CONTRIBUTING.md

File metadata and controls

118 lines (67 loc) · 3.57 KB
Raw

Contributing to one-app-dev-proxy

✨ Thank you for taking the time to contribute to this project ✨

📖 Table of Contents

Code of Conduct

This project adheres to the American Express Code of Conduct. By contributing, you are expected to honor these guidelines.

Developing

Installation

  1. Fork the repository one-app-dev-proxy to your GitHub account.

  2. Afterwards run the following commands in your terminal

    $ git clone https://github.com/<your-github-username>/one-app-dev-proxy
$ cd one-app-dev-proxy

    replace your-github-username with your github username

  3. Install the dependencies by running

    $ npm install

  4. You can now run any of these scripts from the root folder.

Generating the build files

  • npm run build

Builds the module into the lib folder.

Running tests

  • npm test

Runs eslint and unit tests on the current branch.

  • npm posttest

Runs linting on the current branch, checks that the commits follow conventional commits and verifies that the package-lock.json file includes public NPM registry URLs.

Submitting a new feature

When submitting a new feature request or enhancement of an existing features please review the following:

Is your feature request related to a problem

Please provide a clear and concise description of what you want and what your use case is.

Provide an example

Please include a snippets of the code of the new feature.

Describe the suggested enhancement

A clear and concise description of the enhancement to be added include a step-by-step guide if applicable. Add any other context or screenshots or animated GIFs about the feature request

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Reporting bugs

All issues are submitted within GitHub issues. Please check this before submitting a new issue.

Describe the bug

A clear and concise description of what the bug is.

Provide step-by-step guide on how to reproduce the bug

Steps to reproduce the behavior, please provide code snippets or a link to repository

Expected behavior

Please provide a description of the expected behavior

Screenshots

If applicable, add screenshots or animated GIFs to help explain your problem.

System information

Provide the system information which is not limited to the below:

  • OS: [e.g. macOS, Windows]
  • Browser (if applies) [e.g. chrome, safari]
  • Version of one-app-dev-proxy: [e.g. 5.0.0]
  • Node version:[e.g 10.15.1]

Security Bugs

Please review our Security Policy. Please follow the instructions outlined in the policy.

Getting in contact

Coding conventions

Git Commit Guidelines

We follow conventional commits for git commit message formatting. These rules make it easier to review commit logs and improve contextual understanding of code changes. This also allows us to auto-generate the CHANGELOG from commit messages.