Added new env variable to separate staging and production discussions #1608
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.
Relates to #1567
As per feedback from Matt W, current implementation stores staging and production discussions in same place which leads to staging rules URL added to the discussion body.
I think the best way to avoid this issue or any staging and production crossing issues is we can store staging discussions in separate repo.
GISCUS_REPO_NAME
,GISCUS_REPO_ID
,GISCUS_CATEGORY_ID
secrets for each environmentNew behavior:
Figure: Staging URL was added to discussion that this discussion points to production rule as well