So, we're thinking about snapshots.
In the primary Forge repo, we're using fuzzy patching (triggered by the Pupdating flag) to help automate the resolution of most patches to a changed and shifted file.
It works by finding the closest context match (the surrounding area around a patch hunk) if there is no exact match to target. If there is no "close" match, the patch goes to a rejects folder for manual resolution by a human operator.
This would help greatly in MCPConfig, perhaps with a lower threshold for failed applications so that common fuzzy patching issues (such as duplicated lines) are less likely to happen.
Switching to fuzzy patching, combined with incremental patches (described in another issue) will mean that the 1.19-pre1 to 1.19-rc2 update would have roughly 3 files rather than roughly 60.
So, we're thinking about snapshots.
In the primary Forge repo, we're using fuzzy patching (triggered by the Pupdating flag) to help automate the resolution of most patches to a changed and shifted file.
It works by finding the closest context match (the surrounding area around a patch hunk) if there is no exact match to target. If there is no "close" match, the patch goes to a rejects folder for manual resolution by a human operator.
This would help greatly in MCPConfig, perhaps with a lower threshold for failed applications so that common fuzzy patching issues (such as duplicated lines) are less likely to happen.
Switching to fuzzy patching, combined with incremental patches (described in another issue) will mean that the 1.19-pre1 to 1.19-rc2 update would have roughly 3 files rather than roughly 60.