March 15-03-2019

[shaliniiit]

Attendance for 15th March 2019.

[shaliniiit]

Changes made.

[SpandanKumarSahu]

@shaliniiit , it is not a good practice to send a pull request from your master to the master branch of the source repo.
You can undo the commit, by using git reset, then create a separate branch, make the necessary changes in the new branch and then send a pull request to merge your new branch with the source repo's master branch.

If you've any doubts, you can revisit the tutorial on git and github, or I can explain again. This is the first merge on this repository, which is why I wanted to maintain the standard practices, so that from next time everyone can follow the standard procedure.

[shaliniiit]

Okay. I will do the above.Thanks. [image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&> 17/03/19, 17:02:27

…

On Sun, 17 Mar 2019 at 15:40, SpandanKumarSahu ***@***.***> wrote: @shaliniiit <https://github.com/shaliniiit> , it is not a good practice to send a pull request from your master to the master branch of the source repo. You can undo the commit, by using git reset, then create a separate branch, make the necessary changes in the new branch and then send a pull request to merge your new branch with the source repo's master branch. If you've any doubts, you can revisit the tutorial on git and github, or I can explain again. This is the first merge on this repository, which is why I wanted to maintain the standard practices, so that from next time everyone can follow the standard procedure. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AfCiiim6jTCSJQ8L-7yyKiBn6IYfT8Qhks5vXhSagaJpZM4b2why> .