Answers.Body: <p>We're seeing this issue in relation to the <a href="https://plugins.craftcms.com/super-table" rel="nofollow noreferrer">Super Table</a> plugin. This one generates a new <code>changedFieldIndicator</code> every time a super table block type is saved. If a super table field inside a matrix block is changed, the matrix block gets a new <code>changedFieldIndicator</code> as well, so saving a matrix field with some super table fields inside it results in a lot of noise in every pull request.</p>
  <p>I've <a href="https://github.com/verbb/super-table/issues/500" rel="nofollow noreferrer">raised this issue</a> in the Super Table GitHub repository. If you're seeing the same issue, please upvote it or provide additional information if I've missed anything.</p>
  <p><a href="https://github.com/verbb/super-table/issues/500" rel="nofollow noreferrer">https://github.com/verbb/super-table/issues/500</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-01-23T16:36:33.853Z
Answers.LastActivityDate: 2023-01-23T16:36:33.853Z
Answers.UserDisplayName: MoritzLost
Body: <p>When we're making changes to the Craft config, <code>changedFieldIndicator</code> is often the culprit of many changes, and makes pull requests &quot;larger&quot; or more complicated than they need to be.</p>
  <p>Is this expected or is there a way to avoid this?</p>
  <p><a href="https://i.sstatic.net/ryEzz.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ryEzz.png" alt="changedFieldIndicator" /></a></p>
  
Tags: <field><config><fieldtypes><projectconfig><git>
Title: changedFieldIndicator change on every commit
ThreadText: # changedFieldIndicator change on every commit
  
  (Asked by: username_0 on 2023-01-23)
  
  When we're making changes to the Craft config, `changedFieldIndicator` is often the culprit of many changes, and makes pull requests "larger" or more complicated than they need to be.
  
  Is this expected or is there a way to avoid this?
  
  [![changedFieldIndicator](https://i.sstatic.net/ryEzz.png)](https://i.sstatic.net/ryEzz.png)
  
  **Tags:** field, config, fieldtypes, projectconfig, git
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-01-23. Score: 2
  
  We're seeing this issue in relation to the [Super Table](https://plugins.craftcms.com/super-table) plugin. This one generates a new `changedFieldIndicator` every time a super table block type is saved. If a super table field inside a matrix block is changed, the matrix block gets a new `changedFieldIndicator` as well, so saving a matrix field with some super table fields inside it results in a lot of noise in every pull request.
  
  I've [raised this issue](https://github.com/verbb/super-table/issues/500) in the Super Table GitHub repository. If you're seeing the same issue, please upvote it or provide additional information if I've missed anything.
  
  <https://github.com/verbb/super-table/issues/500>
  
  
  ---
  
  