The last (latest) commit on the master branch is still Bump sonarsource/sonarcloud-github-action from 1.5 to 1.6 * apache/daffodil@303cb5a<https://github.com/apache/daffodil/commit/303cb5ab404336860195d65819505dfbfd8dab66> which broke CI because it was missing one change. After I merge the new pull request Bump sonarsource/sonarcloud-github-action from 1.5 to 1.6 by dependabot * Pull Request #598 * apache/daffodil<https://github.com/apache/daffodil/pull/598>, I don't want to have two sequential commits touching some of the same files; I think we should consider these two commits one unit of change, not two.
I want to squash these two commits together (last and newest) so we'll have only a single commit in history. I have already performed the squash within the pull request itself (instead of git rebase -i asf/master, I did a git rebase -i asf/master~1). Once I push that new commit to the dependabot branch and merge the new pull request, I believe we will have only one commit in history with the title "Bump sonarsource/sonarcloud-github-action from 1.5 to 1.6". May I have a +1 to proceed as proposed above? John
