Skip to content

Latest commit

 

History

History
25 lines (14 loc) · 1.08 KB

CONTRIBUTING.md

File metadata and controls

25 lines (14 loc) · 1.08 KB

Pull Request Steps

NOTE: Make sure every change is covered by a unit test.

  1. Fork the repo, create a new branch from develop, make changes, add tests, commit, and submit a Pull Request (to develop)

  2. New Pull Requests will automatically trigger a Travis CI Build

  3. If the build fails, look at the Build Logs. Changes will not be merged unless the build passes

  4. If the build succeeds, the pull request will be reviewed, and when merged will be automatically pushed to the production server at api.launchdashboard.space

Suggestions for new features, data or telemetry

Add a comment with your addition to on the Features, Data and Telemetry Suggestions issue

Corrections

Open a new issue on Launch-Dashboard-API/issues

Have any questions?

Open a new issue here. Please mark it with a 'Question' tag.