With #13, we have removed support for custom changes in templated files because the initial implementation was too cumbersome.
However, for some files, custom changes are all but inevitable. In this issue, we lay out our strategy for adding support for this feature.
As mentioned in #4 (comment), we need a commit on which we can base the update-mqt-templates branch that this repository's Action creates:
We could force this setup by following these steps:
- Remove all templated files from a given repository.
- Add a version of each file without custom changes. Tag this commit.
- Add custom changes again.
Note that this will only be necessary for files for which we want to support custom changes.
Once we have a common base for templating and custom changes, potential conflicts between the two will present as merge conflicts. This is desired, as pointed out in munich-quantum-toolkit/core#1005 (comment).
With #13, we have removed support for custom changes in templated files because the initial implementation was too cumbersome.
However, for some files, custom changes are all but inevitable. In this issue, we lay out our strategy for adding support for this feature.
As mentioned in #4 (comment), we need a commit on which we can base the
update-mqt-templatesbranch that this repository's Action creates:Note that this will only be necessary for files for which we want to support custom changes.
Once we have a common base for templating and custom changes, potential conflicts between the two will present as merge conflicts. This is desired, as pointed out in munich-quantum-toolkit/core#1005 (comment).