require-automatic-updates doesn't understand when the condition is re-checked

[Skalman]

Tell us about your environment

• ESLint Version: v6.1.0
• Node Version: v10.14.1
• npm Version: v6.7.0

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration:

Configuration

{
  "parserOptions": {
    "ecmaVersion": 2018
  },
  "rules": {
    "require-atomic-updates": "error"
  }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

let i = 0;
async function f() {
	if (i) {
		await g();
		if (i) {
			i = 0; // ERROR HERE
		}
	}
}

npx eslint eslint-bug.js

What did you expect to happen?

No error. I'm re-checking the condition after the await, so now I'm sure that the variable contains what I expect it to contain.

What actually happened? Please include the actual, raw output from ESLint.

  6:4  error  Possible race condition: `i` might be reassigned based on an outdated value of `i`  require-atomic-updates

✖ 1 problem (1 error, 0 warnings)

Are you willing to submit a pull request to fix this bug? No

[eslint-deprecated]

Unfortunately, it looks like there wasn't enough interest from the team
or community to implement this change. While we wish we'd be able to
accommodate everyone's requests, we do need to prioritize. We've found
that issues failing to reach accepted status after 21 days tend to
never be accepted, and as such, we close those issues.
This doesn't mean the idea isn't interesting or useful, just that it's
not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.