fprettify

[sseraj]

Purpose

Formatting the Fortran code with fprettify

Expected time until merged

1 week

Type of change

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (non-backwards-compatible fix or feature)
• [x] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no API changes)
• [ ] Documentation update
• [ ] Maintenance update
• [ ] Other (please describe)

Testing

Current tests pass

Checklist

• [x] I have run flake8 and black to make sure the code adheres to PEP-8 and is consistently formatted
• [x] I have run unit and regression tests which pass locally with my changes
• [ ] I have added new tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation

[codecov[bot]]

Codecov Report

Merging #63 (d5ed969) into main (05c8e24) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #63   +/-   ##
=======================================
  Coverage   79.95%   79.95%           
=======================================
  Files           4        4           
  Lines         414      414           
=======================================
  Hits          331      331           
  Misses         83       83           

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

[gawng]

Does a separate PR need to be made so that the git blame history doesn't just have your name on every formatted FORTRAN file?

[sseraj]

Does a separate PR need to be made so that the git blame history doesn't just have your name on every formatted FORTRAN file?

Yes, that's right. We have to add the squashed commit to git-blame-ignore-revs.

[lamkina]

I don't know how to do the git-blame-ignore-revs thing so I'll let @sseraj or @gang525 merge this so I don't screw things up.

[sseraj]

I don't know how to do the git-blame-ignore-revs thing so I'll let @sseraj or @gang525 merge this so I don't screw things up.

We won't know the hash until we merge