Play state#105
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/atapas/react-play/AuxecB5hAATzadsMSJYqn4tM4p3g |
Build fail log[12:25:09.308] Cloning github.com/atapas/react-play (Branch: playState, Commit: ebbe0da) |
atapas
left a comment
There was a problem hiding this comment.
@Abhishek-90 You haven't resolved merge conflicts correctly.. hence lots of unnecessary changes went in. Please take care. If you have issues in resolving merge conflicts, see some videos on how to do them. If the problem persists, scrap this branch and PR and create a new fresh one.
|
@atapas I have push the new changes with conflicts resolved |
I see my older comments are not taken care. |
|
@atapas can you please elaborate ? |
|
atapas
left a comment
There was a problem hiding this comment.
Given a comment
You are comitting yarn lock and package lock, why? Please do not commit these files if you haven't changed the package.json file. If you pull the latest from the main, these two files shouldn't appear in your to be committed list.
already have state.css file
|
@atapas Initially I used State.css but changed it to state.css on your suggestion. I meant to delete it from Github, Now I have deleted State.css about yarn.lock, I deleted it from committed list, I am not sure why it is still showing |

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
Checklist: