The intended mode of operation for the Issue template headings was
for the local to over-ride the remote. This is different to the other
fields, such as maintainers.
This change adds the test to highlight the issue and addresses the
issue in MergeDerekRepoConfigs.
Signed-off-by: Richard Gee richard@technologee.co.uk
Description
The intended mode of operation for the Issue template headings was for the local to over-ride the remote. This is different to the other fields, such as maintainers.
This change adds the test to highlight the issue and addresses the issue in MergeDerekRepoConfigs.
Motivation and Context
A recent issue (https://github.com/alexellis/go-execute/issues/10) indirectly highlighted that the merging of local and remote configs was producing a superset which included duplicate headings
How Has This Been Tested?
Wrote the test, and ran it:
Note the
got
set is a merge of the remote and local so includes#2
twice.Amended
MergeDerekRepoConfigs()
so that ifrequired_in_issue
is set locally then those values will take precedence. Re-ran the test:Ran a build using the Dockerfile.
Types of changes
Checklist:
git commit -s