This repository was archived by the owner on Jul 31, 2025. It is now read-only.
chore: Modified bug issue template to add checkbox to report potential regression. #5325
Conversation
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
ashishdhingra
deleted the
user/ashdhin/IssueTemplateRegressionCheckbox
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
[IMPORTANT] We announced the upcoming end-of-support for AWS SDK for Go v1. We are no longer accepting PRs for the v1 SDK.
potential-regressionwhen issue is created/edited.NOTE:
potential-regressionwould need to be created manually (we could use color#FF6700and descriptionMarking this issue as a potential regression to be checked by team memberto make it consistent across SDK repos)Label
potential-regressionwould make issue standout in the list and help engineers to triage potential high severity issues effectively.For repos getting deprecated, these would still be accepting security updates and/or crritical service updates. These could essentially cause breaking changes.