Thanks for this fix @msupernaw but you opened a PR to main using a feature branch off of dev. This seems like it is a true hot fix and thus your branch needs to be rebased to main and force pushed.

@kellijohnson-NOAA I meant to create the PR to dev.

Codecov Report

❌ Patch coverage is 60.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 85.96%. Comparing base (e0be2a1) to head (0d7f735).
⚠️ Report is 3 commits behind head on main.

@@            Coverage Diff             @@
##             main    #1070      +/-   ##
==========================================
- Coverage   85.97%   85.96%   -0.01%     
==========================================
  Files          81       81              
  Lines        7884     7887       +3     
  Branches      515      517       +2     
==========================================
+ Hits         6778     6780       +2     
- Misses       1098     1099       +1     
  Partials        8        8              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

But the PR should be to main because it fixes version 0.7.0. So, the DESCRIPTION file should also be edited to be 0.7.1 because it is a hot fix and not a new version. If it goes into dev first then it will be part of version 0.8.0. Also, the spell check file needs to be updated.

This PR needs to be rebased to main because it was originally based off of a feature branch off of dev.

git fetch -a
git checkout dev-json-hot-fix
git rebase origin/main

@kellijohnson-NOAA rebased to main yesterday. I just verified the SHAs are the same, let me know if there are issues.

Thanks @msupernaw I didn't realize that because you made a feature branch off of dev and dev has the exact same history as main that it won't allow the removal of those two commits (see below) with a straight rebase. You need to do an interactive rebase and remove those commits. Let me know if you need help doing that. Gemini can also provide directions

Gemini instructions
Step 1: Start the Interactive Rebase
Make sure you are on your feature branch and run the rebase command against main:

git checkout your-feature-branch
git rebase -i main

Step 2: Drop the Unwanted Commits
A text editor (usually Vim, Nano, or VS Code) will open showing a list of commits that are on your branch but not on main. It will look something like this:

pick a1b2c3d Fix layout bug (Your feature commit)
pick e5f6g7h Update dependencies (The unwanted dev commit 1)
pick i8j9k0l Add logging (The unwanted dev commit 2)
pick m1n2o3p Update documentation (Your feature commit)

Locate the two commits from dev that you want to remove. Change the word pick to drop (or just d) next to those commits Leave your actual feature commits as pick.
It should now look like this:

pick a1b2c3d Fix layout bug
drop e5f6g7h Update dependencies
drop i8j9k0l Add logging
pick m1n2o3p Update documentation

Step 3: Save and Exit
If in Vim: Press Esc, type :wq, and hit Enter.
If in Nano: Press Ctrl+O, Enter to save, then Ctrl+X to exit.
If in VS Code: Just save the file and close the tab.

Git will now rewrite your branch history, removing the "dropped" commits and keeping only your feature work.

Step 4: Force Push
Because you have rewritten the history of the branch, you cannot do a normal push. You must force push to update the remote server:

git push --force-with-lease origin your-feature-branch

(Note: --force-with-lease is safer than --force because it checks that no one else has pushed code to that branch in the meantime.)