# Forced rustfmt is a roadblock to contributing

**URL:** <https://internals.rust-lang.org/t/forced-rustfmt-is-a-roadblock-to-contributing/11913>\
**Category:** tools and infrastructure\
**Created:** [February 28, 2020, 8:43pm UTC](https://internals.rust-lang.org/t/forced-rustfmt-is-a-roadblock-to-contributing/11913 "2020-02-28T20:43:05Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![bascule](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/bascule/32/3057_2.png) [@bascule](https://internals.rust-lang.org/u/bascule)\
**Post date:** [February 29, 2020, 1:52am UTC](https://internals.rust-lang.org/t/forced-rustfmt-is-a-roadblock-to-contributing/11913/16 "2020-02-29T01:52:37Z")

</div>

> [@matklad](#):
>
> You can run `rustfmt` during `cargo test`

Yes there are all sorts of ways to avoid forgetting to `rustfmt` before committing, BUT...

`rustfmt` is work a robot can do, so instead of giving people instructions, and failing their PRs if they don't follow them, a robot could automatically apply the fixes instead.

> [@Eh2406](#):
>
> Or as I have suggested before while bors is merging it can run rustfmt on the results. PRs do not need to be formatted, master is always formated.

Yes! This!

---

_[View the full topic](https://internals.rust-lang.org/t/forced-rustfmt-is-a-roadblock-to-contributing/11913)._