After manually editing files to resolve a merge conflict, what is the *next essential Git commandyou must run before you can complete the merge commit?

After manually editing files to resolve a merge conflict, the next essential Git command you must run is `git add` for each file you modified. A merge conflict occurs when Git cannot automatically combine differing changes to the same part of a file from two branches that are being merged. When you manually edit a conflicted file, you remove the special conflict markers that Git inserts (like `<<<<<<<`, `=======`, `>>>>>>>`) and combine the desired changes from both branches into a single, coherent version. However, simply saving these changes in your working directory is not enough for Git to recognize that the conflict has been resolved. The `git add` command is used to stage these manually resolved changes. The staging area, also known as the index, is an intermediate area where Git collects all the changes that will be included in the next commit. By running `git add <filename>` for each conflicted file, you are explicitly telling Git that you have successfully addressed the conflict in that specific file and that its current state in your working directory is the final, intended version to be part of the merge. Once all conflicted files have been staged using `git add`, Git understands that the entire merge conflict has been fully addressed, and you can then proceed to complete the merge by creating the merge commit.