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
docs: Add "Keeping Branch Up to Date and Resolving Merge Conflicts" section #123
docs: Add "Keeping Branch Up to Date and Resolving Merge Conflicts" section #123
Conversation
β¦m/adiati98/guestbook into docs/add-resolve-conflict-section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @adiati98! :) The guide looks pretty good so far! :) I just gave some feedback in my inline comments. I hope you find them helpful! :)
β¦s/add-resolve-conflict-section
β¦flicts Add What Next section
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CBID2 I made some fixes for you to check out. Thank you!π
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You got some merge conflicts on here that need solving @adiati98
Thanks! Now just need to discuss about the screen recordings before I make this ready for review ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I think that adding screenshots are helpful, they aren't necessary especially if this remains in the readme. With the README, it's important that we don't overwhelm contributors with too much. I think that screenshots will start to make the README feel too long. I do have this blog post written about it that can be referenced here that has screenshots.
Depending on how things change here, we might want to add another folder in the repo for community-resources that includes translations and the info here, but I think for now, the repo is still manageable.
|
@BekahHW this PR can't be merged because there were unresolved reviews from @CBID2. Now I closed them as resolved. You can try again. If it doesn't work, you need to override @CBID2 review. I did this before in one PR, but forgot to take note. Update: FYI @BekahHW @CBID2,
And don't forget to give brief description why you want to dismiss the review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great now @adiati98! :) Sorry for taking so long. I thought I approved your PR. I guess I did in my head lol π


Description
This PR adds the Keeping Branch Up to Date and Resolving Merge Conflicts section to walk through the process for this project.
Note for Reviewers
Because there is CLI involved for this project, screen recordings (GIFs) will be more clear than screenshots. So there will be GIFs (or video walkthrough) provided, but how to add them here is to be advised.
One of the steps to resolve conflict is to move contributor's profile details to the last list in the contributors array. This step is necessary because without it, the PRs that are awaiting for review have to update their branch locally and run
npm run contributors:generateto regenerate the badge. It will be too complicated and discouraging for this simple project --> this is one of the reasons that the process won't be too clear with screenshots.Once this PR is merged, there will be another PR following to add GIFs.
Videos walkthrough are planned to replace GIFs in the future.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Refers to #118
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?