-
Notifications
You must be signed in to change notification settings - Fork 14
04 Submit a PR
Assumptions:
- You have contributor access to the repository
When submitting a PR to the repository, describe the main goal of the PR as the title. For the body of the PR, describe in greater details what changes are going to be implemented. The body can be 3-4 sentences that describes all of the commits in this branch.
Reference the issue number if available.
For example:
Add interactivity to welcome message
This PR adds an interactivity UI to the welcome message to give our on-boarding experience more of a tourist-guide feel. Move messages to their own file and reference in the functions accordingly as a response when
/welcome
is requested.Addresses Issue #3.
- Assign yourself as the
Assignee
- Set the appropriate label. For example,
Ready for review
if finished,Work in progress
if still in progress,Question
for feedback, etc. - Let us know in #cb-code if you'd like some feedback or a review.
It is important that we have a code review process both as a learning experience and for QA purposes.
See a typo or could use more clarification? File an issue.