Hello,

this is a feature request, as a spinoff of closed service desk issue:

https://support.atlassian.com/servicedesk/customer/portal/23/JST-227786

We are integrating Github/Bitbucket Cloud with JIRA cloud. As we follow the Git Flow development model, we find ourselves rebasing our feature branches on the `develop` branch daily. The obsolete (and unreachable) commits still show on the Git integration section on the issue. This is confusing, especially if the number of commits is large, and if the number of rebases is also large, as I end up seeing dozens and dozens of commits, instead of the real, "reachable" commits.

I have used JIRA (on-premise) integrated with on-premise Stash, and I am quite sure that we never had this issue.

The support engineer I spoke with in the linked service desk issue adviced me to overcome this by forcing a complete syncing. This works, but this is merely a workaround, as I have to do this all the time.

I would suggest enhancing your Github integration by implementing the same behaviour you are already providing when integrating with Stash (and presumably Bitbucket as well). I believe that it greatly degrades the integration you are providing.