Closed Marauderer97 closed 7 years ago
@jig08 nice to have you onboard but for squashing commits we have the squash and merge option so that won't be a problem ;)
I'd recommend no to use the squash and merge
option for so many commits especially the merge ones. Thanks.
@Marauderer97 Could you pls do the needful ?
Yikes you are on a separate branch can you try to give out some previews since it can be achieved locally pls give some screenshots @marauderer97
Initially the ball was here: Now it is here:
Solves #242
@Abhi2424shek @jig08 I used squash and merge while merging , so that all the commits are merged as one single commit, is this good?
@Marauderer97
squash and merge
option for so many commits especially the merge ones.Follow the guidelines to be a good contributor to any open source project and/or org.
@niccokunzmann Could you pls check who all have the write access to this project ? We'd like to have it limited to protect the sanity :)
@jig08 It is @Marauderer97 @Abhi2424shek and me. Yes, we should not merge our PR so fast and wait for at least a day but I think, they know it now and will follow this rule :) They support the work flow as we need to merge fast here because flappy.svg can not be merged automatically but is changed almost every time.
@Marauderer97 squashing is good, sure.
@jig08 My most sincere apologies Firstly, I inferred from your conversation with @Abhi2424shek that you wanted me to squash and merge, and that is why i did it. Secondly, I don't understand which commit message you are talking about? I thought you guys had asked for screenshots, and a related issue which this solves and I commented both of them.. Lastly, most of the things fixed were very minute errors, mostly in layers I had contributed myself, and simply involved creating new files or changing a single word, which is why I was so confident about the PR. However point duly noted. Will be more careful next time. :)
@Marauderer97
Yes, The review required squashing the commits from your end using the terminal and not the web interface. Each PR should be matched with a single commit before we can merge into master
.
The commit message needed to be changed to be more precise about the changes being done and keep a clean & lucid history, please read about git/github basics. It shall definitely help you improvise.
Thanks.
The PR solves the following problems: