Similar example false negative situation pointed in issue #13309 :

foo = 1 # should have an offense
foo = 2
bar {
  foo = 3
}

The issue here is that Lint/UselessAssignment checks if assignments have been used, however, the assignments check it based on the assignment having been referenced or the variable being used in a block. So, the false negative occurs because of the first assignment being unused but having the variable captured in a block. One potential way of solving this is too track reassignments (a new assignment follows a not referenced assignment).

Fixes #13309.

Before submitting the PR make sure the following are checked:

• The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
• Wrote good commit messages.
• Commit message starts with [Fix #issue-number] (if the related issue exists).
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
• Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.