The "Merge remote-tracking branch" commit is from when you updated from Roll20's "master" branch. Since your pull request is going to the same branch, all it's really doing is helping to avoid merge conflicts. (And, since the devs aren't going to spend time resolving merge conflicts, merge conflicts mean rejected PRs.) The duplicate "#2" commit is simply fixing the Chakra Control roll button and Climb roll button. The summary and description is simply what you entered for the commit, and it can be duplicated between commits, which is presumably what happened to you. What actually identifies the commit is the long hexadecimal number associated with the commit (6448413a94458e2dada5ece53bd661f626dfc0c1 for the first commit "#2", and 6fc2a4ed5503a1e7e8989ec0ddaa0d09965216a1 for the second "#2"). It is possible to ammend your most recent commit in Git, but (I believe) it's only possible from the command line, not the desktop application proper. ("git commit --amend" will add the currently staged changes in the repo to the previous commit, instead of creating a new commit with the current changes.) Git doesn't like amending commits that have been pushed to a remote repo, although you can still force the push (but doing so can cause problems if you're using Git with a team, which is why Git gives an error message outside of forcing it).
