This outlines are indicated to know the credit card approving factors based on our dataset.
There is also a strict no meanness rule. At every step, please be kind and inclusive, even if people are asking not-so-informed questions.
- Open a Issue to discuss where you think might have problems
- You can fork this repo if the problems have been committed by Two of the Members
- Changing the stuff you think that would be a problem
- Open PR
Before you make a substantial pull request, you should always file an issue and make sure someone from the team agrees that it's a problem. If you've found a bug, create an associated issue and illustrate the bug with a minimal reprex.
- We recommend that you create a Git branch for each pull request (PR).
- New code should follow the tidyverse style guide or PEP8 style guide.
- Pull requests should be reviewed by Friday end of day.
- Any revisions should be communicated via GitHub issue or Slack (for urgent updates/notification).
- The proof-reader will review the work on Saturday and ensure that the final version is ready for submission and create the required version tag.
- Submit by Saturday at 6:00 pm.
- a written Slack notice that outlines the violation of the team contract and a reminder of the team contract conditions.
- a meeting to discuss the behaviour and write an agreement to follow the team contract is required by the member.
- to reach out to the lab instructor or TAs of the issues with the teammate
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
These contributing guidelines were adapted from the dplyr contributing guidelines.