🤖 Refactor GitHub Issue Creation Code for Clarity and Efficiency #83888
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.
👋 Hi there! This PR was automatically generated by Autofix 🤖
This fix was triggered by Michi Hoffmann
Fixes SENTRY-3GEH
The
create_issue
method inissues.py
has been refactored to improve code clarity and efficiency. Specifically, the creation of issue data is now encapsulated in a dictionary namedissue_data
, where required fields are set directly and optional fields (assignee
andlabels
) are only included if they have valid values. This reduces redundancy and simplifies the parameters passed to theclient.create_issue
method. Additionally, the code formatting has been cleaned up by removing unnecessary line breaks.If you have any questions or feedback for the Sentry team about this fix, please email [email protected] with the Run ID: 3473.