Updated .gittatributes

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.

[AnonymousCodes911]

fixes: #92
-added necessary attributes.
-replaced the pre-existing function

[kartikmandar]

This also happens not only for jupyter notebook but vscode too.

[AnonymousCodes911]

This also happens not only for jupyter notebook but vscode too.

can you give more details?

[kartikmandar]

What I meant was that not only the jupyter notebook produces unnecessary stuff while browsing through when inspected in git diff, vscode does the same. Is this fix working both for jupyter notebook and vs code?

[AnonymousCodes911]

As per the latest commit, after installing the dependencies, The git diff should not return large changes made to the image file, as per as the issues about the VS code, I think we already have the contingency in .gitignore file, but if you are referring to the state of file ( M,U,Detc.) that are shown in the Source Control tab, I think they can be managed by simply un-staging the changes or you can simply discard them, further you can use git stash push <file_name> this will remove the changes you made and stash them.
Refer comment
If you were referring to something else, please share a screenshot!

[kartikmandar]

I guess the same goes for the vs code, will see it after the merge on how is this working. Also for making changes nano and vim works quite good in avoiding this unnecessary diff.