Skip to content

(fix): remove no else raise and no else return rules from .pylintrc#3525

Closed
pushpitkamboj wants to merge 4 commits intoaugurlabs:mainfrom
pushpitkamboj:fix_linter
Closed

(fix): remove no else raise and no else return rules from .pylintrc#3525
pushpitkamboj wants to merge 4 commits intoaugurlabs:mainfrom
pushpitkamboj:fix_linter

Conversation

@pushpitkamboj
Copy link
Copy Markdown
Contributor

Fix #3521
Removed rules R1720 and R1705 from .pylintrc, disabling suggestions to remove raise or return blocks.

Signed-off-by: PredictiveManish <manish.tiwari.09@zohomail.in>
Signed-off-by: PredictiveManish <manish.tiwari.09@zohomail.in>
Copilot AI review requested due to automatic review settings January 7, 2026 18:06

This comment was marked as spam.

Signed-off-by: pushpit kamboj <pushpitkamboj@gmail.com>
@MoralCode MoralCode changed the title (fix): changed config in .pylintrc (fix): remove no else raise and no else return rules from .pylintrc Jan 8, 2026
Copy link
Copy Markdown
Collaborator

@MoralCode MoralCode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR and for including documentation links in the PR so i can verify the (annoying) copilot comments

Comment on lines 49 to 52
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is not related - can you update your PR to only include the changes to the pylintrc?

@MoralCode MoralCode added the redundant PR is submitted in parallel with another mutually exclusive PR label Jan 8, 2026
Signed-off-by: pushpit kamboj <pushpitkamboj@gmail.com>
@pushpitkamboj
Copy link
Copy Markdown
Contributor Author

sorry it was my mistake, thought to raise a new clean PR which will be better to have clean history.
#3533
will close this PR

@guptapratykshh
Copy link
Copy Markdown
Contributor

Hey @pushpitkamboj, for future reference, you did not need to open a new PR. It is perfectly fine to address feedback in the same PR. This keeps the conversation thread intact.

@MoralCode
Copy link
Copy Markdown
Collaborator

Closing as superseded by #3533

@MoralCode MoralCode closed this Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

redundant PR is submitted in parallel with another mutually exclusive PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Change linter config to NOT suggest removing "dangling else" blocks

5 participants