Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🤖 Refactor GitHub Issue Creation Code for Clarity and Efficiency #83888

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

sentry-autofix[bot]
Copy link
Contributor

👋 Hi there! This PR was automatically generated by Autofix 🤖

This fix was triggered by Michi Hoffmann

Fixes SENTRY-3GEH

The create_issue method in issues.py has been refactored to improve code clarity and efficiency. Specifically, the creation of issue data is now encapsulated in a dictionary named issue_data, where required fields are set directly and optional fields (assignee and labels) are only included if they have valid values. This reduces redundancy and simplifies the parameters passed to the client.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.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants