Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v1.0][T15-B2] Smart Insurance Collection #61

Open
wants to merge 299 commits into
base: master
Choose a base branch
from

Conversation

jstarw
Copy link

@jstarw jstarw commented Mar 8, 2018

No description provided.

@nus-se-pr-bot
Copy link

Hi @jstarw, your pull request title is invalid.

For phase A, it should be in the format of [Learning Outcome ID][Team ID] Your Name, where [Learning Outcome ID] has no dashes or spaces (e.g. [W3.1a]) and [Team ID] has one dash only and no spaces (e.g. [W14-A2] means Wednesday 2pm (14 hrs), Phase A, Team 2).

For phase B, it should be in the format of [v1.x][Team ID] Product Name, replacing v1.x with current milestone progress.

Please follow the instructions given strictly and edit your title for reprocessing.

Submit only one learning outcome per pull request (unless otherwise stated in instructions) and do remember to create your branches from the commit where the master branch is pointing at so that each PR you submit only consist of commits meant for the activity.

Note: this comment is posted by a bot. If you believe this is done in error, please create an issue at cs2103-pr-bot and add a link to this PR.

@jstarw jstarw changed the title [v1.x][T15-B2] Smart Insurance Collection [v1.0][T15-B2] Smart Insurance Collection Mar 8, 2018
@yuxiangSg
Copy link

sorry, i think i commited with another github account,

@yuxiangSg
Copy link

should i push again with the correct account or should i just make sure any further commit is the right account @madsonic

@madsonic
Copy link

@yuxiangSg push it again with the correct account

@madsonic
Copy link

madsonic commented Mar 10, 2018

@yuxiangSg u can do it directly from your personal repo and not have to merge into the team repo if it is individual LO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants