Ignore the output logs

[wkearn]

These get generated by the tests, but we don't really want to save or check them, so it is best to ignore them.

[jkhillier]

Hi Will - Branch "JH_refactor_3" is one commit ahead. So, I don't want to do further commits to complicate things. It has some changes to swt.c, but the two output files you don't want. What do you want me to do? Remove the output files and commit again? You've told me how to do this, but I'm just not sure if it will help (i.e. overwrite the last commit) or will mess things up. Please advise. Thank you. John

[wkearn]

@jkhillier: You have done everything correctly so far. Your JH_refactor_3 branch is one commit ahead of main, and that one commit is the one (af5a31e) that you currently have in your pull request (#15). You should be able to git rm test/output.txt test/seamounts_output.txt then git commit to remove the output logs. This will add a commit to your branch and put you two commits ahead of main.

Then I will merge #15 first, followed by this pull request (#16), so you shouldn't have to do anything weird beyond removing the output files.

Once #16 is merged, you won't be able to commit the test/output.txt and test/seamounts_output.txt files, so this kind of thing should be less likely to happen in the future.

[jkhillier]

Thank you William - The clarification on the nature of what 'commit' does was what I needed. Second commit done with output files removed. If I'm correct, I don't need to do another pull request .... but please let me know if I've got another action here. John