fix(issue-template): remove envoy references from bug report#3
Merged
Conversation
The org-wide bug report template referenced envoy (an unrelated project) in three places — a hardcoded link in the search-existing-issues header, the steps-to-reproduce placeholder, and the environment "version" field. Because this template is the org baseline, every member repo without its own template inherits these stale references on its issues page. - Drop the hardcoded envoy issues link; issue forms cannot template the current repo, so use neutral guidance instead. - Replace `envoy --force` with a generic `<command>` placeholder. - Rename "envoy version" to "Affected project version". Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
ISSUE_TEMPLATE/bug_report.ymlreferencedenvoy(an unrelated project) in three places. Because this template is the org baseline, every member repo without its ownbug_reportinherits these stale references on its issues page.ISSUE_TEMPLATE/bug_report.yml:castastrophe/envoy/issuesURL. Issue forms can't expand${{ github.repository }}, so a per-repo dynamic link isn't an option — neutral wording ("search existing issues for this project") avoids pointing users at the wrong repo.envoy --force→<command>.envoy version→Affected project version.config.yml,documentation.yml,feature_request.yml) are unchanged.Test plan
ISSUE_TEMPLATE/and confirm the bug report form shows noenvoyreferences..githubrepo itself and confirm the three updated fields render correctly.feature_request.yml,documentation.yml, andconfig.ymlstill render unchanged.🤖 Generated with Claude Code