Because many of the project's unit tests depend on sensitive API keys, and Travis CI has no easy way to handle this sensitive data from external pull requests, there are some gymnastics required to submit a pull request.
- Fork the repo
- Cut a namespaced feature branch from master
- bug/...
- feat/...
- test/...
- doc/...
- refactor/...
- Make commits to your feature branch. Please ensure commit messages are written in present tense.
- When you've finished with your fix or feature, rebase upstream changes into your branch. submit a pull request
to the
developbranch. Include a description of your changes. - Your pull request (PR) will be reviewed by another maintainer. A maintainer will create a new namespaced branch, alter your PR's destination to be that branch, and merge it.
- A maintainer will make an essentially identical PR from your new namespaced branch
on the main repo to the
developbranch. This ensures that Travis will run its tests with the necessary API keys. - Once the pull request has been reviewed, it will be merged by another member of the team.
For any additional questions, related to workflow or otherwise, feel free to open an issue to start a conversation.