closes #108 Created CHANGELOG.md with the last five changes

[Jiwoo22]

Created a changelog using the format from keep a changelog

• Note each version tag in the changelog may contain (Added, Changes, Removed) sub sections every time changes are made to the repo.

[Jiwoo22]

This is my first PR in my life

[mnicpt]

Congrats, @jchoi136, on your first PR!🚀

[apuntovanini]

Well done @jchoi136!!

If I may, the PR fixes an issue but we'll have the same problem in few commits/releases unless this becomes an automated process. @mnicpt what do you think about https://github.com/atlassian/changesets or https://github.com/conventional-changelog/standard-version?

[songz]

ping @bluepnume any thoughts on @apuntovanini 's comments? I feel like commit automation may not be as human readable as user written updates, especially when sometimes commits usually parts of an overall feature and only the overall feature is important enough to be written.

[bluepnume]

I worry without some kind of automation, we'll end up falling behind with manually keeping a change-log up to date. Plus, we have "squash and merge" set as default on all of these repos; so any PRs should ideally cover an entire, atomic change that should fit neatly into a change-log. We do need to be good at enforcing good commit/pr messages, though.

[apuntovanini]

Actually @changesets/cli (for instance) is automated in the sense that enforces a standard for publishing changesets with proper commits, and automatically builds changelogs. I find it very useful, but, yes, it's strongly related to how contributing / merging and releasing is structured. You can see some examples in https://atlassian.design/components/banner/code (click on changelog on the right)
Thanks for the discussion!