# Introducing Codee Formatter for Fortran **URL:** \ **Category:** Announcements\ **Created:** [April 24, 2025, 8:05am UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619 "2025-04-24T08:05:57Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![alvrogd](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@alvrogd](https://fortran-lang.discourse.group/u/alvrogd)\ **Post date:** [April 24, 2025, 8:05am UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/1 "2025-04-24T08:05:57Z")
Hello everyone! We at [Codee](https://www.codee.com/) have been working on something we’re excited to share: the Codee Formatter for Fortran, now live and completely free to use! It has been a collaborative effort with the community from the start, and this launch wouldn’t have been possible without feedback, ideas, and testing from many of you here. Thank you for your participation! With the Codee Formatter, you can easily clean up your code to keep it consistent, improving readability and speeding up code reviews: - Try it for free here: [https://codee.com/codee-formatter](https://codee.com/codee-formatter) - Compare it against other Fortran formatters: [Introducing Codee Formatter for Fortran – Now Part of Codee 2025.2 - Codee](https://www.codee.com/introducing-codee-formatter-for-fortran-codee-2025-2) - Explore its features and integrations in the documentation: [Codee Formatter | The platform for code correctness, modernization, and optimization](https://docs.codee.com/formatter) As mentioned in the blog post, feel free to also check out our [Codee Analyzer](https://www.codee.com/codee-analyzer/), which allows you to dive into static code analysis to further improve your code. Let us know what you think, we’re listening! ---
**Author:** ![fedebenelli](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fedebenelli/32/1823_2.png) [@fedebenelli](https://fortran-lang.discourse.group/u/fedebenelli)\ **Post date:** [April 27, 2025, 7:57am UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/2 "2025-04-27T07:57:58Z")
> [@alvrogd](#): > > improving The feedback and acceptance of suggestions from Codee during the development of their formatter was great! I will probably start using it as my default formatter now ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [April 27, 2025, 7:59pm UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/3 "2025-04-27T19:59:31Z")
Nice. ### Suggestion: I like an option to make all the elements of a character array the same length most of the time, which I do not think any of the formatters do, as in changing ```fortran text=[character(len=80) :: & 'and a one and a',& 'two ',& 'and a three!']) ``` into ```fortran text=[character(len=80) :: & 'and a one and a ',& 'two ',& 'and a three ']) I not aware of any formatter being able to do that. ``` ---
**Author:** ![alvrogd](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@alvrogd](https://fortran-lang.discourse.group/u/alvrogd)\ **Post date:** [April 29, 2025, 12:23pm UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/4 "2025-04-29T12:23:33Z")
We’re glad to hear that you’re having a great experience with our Formatter! ---
**Author:** ![alvrogd](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@alvrogd](https://fortran-lang.discourse.group/u/alvrogd)\ **Post date:** [April 29, 2025, 12:24pm UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/5 "2025-04-29T12:24:59Z")
Right now, we’re working on alignment features that could make your example look like: ```auto text=[character(len=80) :: & 'and a one and a', & 'two ', & 'and a three!']) ``` Would that cover your needs, or do you require the inclusion of spaces inside the character array? Doing so would _change_ the actual meaning of the code, which is beyond the typical scope of a formatter. Let us know what would work best for you! ---
**Author:** ![urbanjost](https://avatars.discourse-cdn.com/v4/letter/u/0ea827/32.png) [@urbanjost](https://fortran-lang.discourse.group/u/urbanjost)\ **Post date:** [April 29, 2025, 12:35pm UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/6 "2025-04-29T12:35:12Z")
That would work as well, and would work for user-defined types where the string length is significant. Adding the spaces would not change the meaning of standard strings however. I prefer aligning :: in declarations as well, but not always when there are long outliers that cause an excessive amount of white space (where I have never consciously defined “excessive”) so it will be interesting to follow what features you come up with. ---
**Author:** ![alvrogd](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@alvrogd](https://fortran-lang.discourse.group/u/alvrogd)\ **Post date:** [April 29, 2025, 2:32pm UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/7 "2025-04-29T14:32:51Z")
> Adding the spaces would not change the meaning of standard strings however. Sorry about the confusion! I didn’t realize that `len=80` would have that effect here. > That would work as well Great! We will also keep the `::` alignment idea in mind; several users have asked for it, so it would be a great addition. > so it will be interesting to follow what features you come up with. We’ll be sure to keep this community and our other channels updated with any Codee news 🙂 We usually make public announcements every three months, but push minor releases once or twice a month, so that Codee is constantly getting new features. For the latest updates, we always have the [changelog](https://docs.codee.com/changelog) available on our website. ---
**Author:** ![alvrogd](https://avatars.discourse-cdn.com/v4/letter/a/e19adc/32.png) [@alvrogd](https://fortran-lang.discourse.group/u/alvrogd)\ **Post date:** [June 20, 2025, 8:25am UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/8 "2025-06-20T08:25:46Z")
Hello everyone! Just a quick update for those who expressed interest 🙂 We’ve just published a 5 min. demo video on using the Codee Formatter in a typical Fortran workflow. It covers: - Command-line usage. - Git integration (`git codee-format`). - VS Code setup. - Enforcing formatting in CI/CD with GitHub Actions. You can watch the demo here: [https://www.youtube.com/watch?v=PvPwMB2BL4M](https://www.youtube.com/watch?v=PvPwMB2BL4M) We hope it’s helpful for those exploring how to integrate consistent formatting into their projects. Remember that our Formatter is free to use: [https://www.codee.com/codee-formatter/](https://www.codee.com/codee-formatter/) As always, we welcome your feedback! ---
**Author:** ![fedebenelli](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/fedebenelli/32/1823_2.png) [@fedebenelli](https://fortran-lang.discourse.group/u/fedebenelli)\ **Post date:** [July 2, 2025, 2:19am UTC](https://fortran-lang.discourse.group/t/introducing-codee-formatter-for-fortran/9619/9 "2025-07-02T02:19:37Z")
> [@alvrogd](#): > > Enforcing formatting in CI/CD with GitHub Actions. Really happy to see that it is possible to enforce formatting in CI! I will take a look