feat(remote): activate integration if remote is set manually #782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Before this change the only way of activating a remote integration (and fetching remote data) used to be incorporating the related variables in a template.
This meant that the changelog context won't contain e.g. GitHub related fields unless you use e.g.
github.contributors
in your template.This PR adds support for enabling the remote integration for the following cases as well:
[remote]
table is configured.--github-repo
)So the following output will contain GitHub variables even with the default template (since the remote is set):
Motivation and Context
closes #780
How Has This Been Tested?
Unit tests, local run.
Types of Changes
Checklist: