Skip to content

feat: in retaliation to→in retaliation for/in response to#3476

Open
hippietrail wants to merge 3 commits into
Automattic:masterfrom
hippietrail:in-retaliation-to
Open

feat: in retaliation to→in retaliation for/in response to#3476
hippietrail wants to merge 3 commits into
Automattic:masterfrom
hippietrail:in-retaliation-to

Conversation

@hippietrail
Copy link
Copy Markdown
Collaborator

Issues

N/A

Description

I heard "in retaliation to" for the first time in a YouTube video, checked to make sure it's a mistake for "in retaliation for" and discovered it's the result of mixing up "in retaliation for" and "in response to".

So both are suggested.

How Has This Been Tested?

cargo test

AI Disclosure

  • I am a human and didn't use any AI.
  • I used LLM features of my editor, but not an agent.
  • I used an AI agent interactively.
  • I am an agent or I got an agent to do the work autonomously.

If Your PR Implements or Enhances a Linter

  • I made up the sentences in the unit tests.
  • The sentences in the unit tests were generated by an AI.
  • I'm using examples from the bug report / feature request.
  • I collected real-world sentences for the unit tests.

Checklist

  • I have performed a self-review of my own code
  • I have added tests to cover my changes
  • I have considered splitting this into smaller pull requests.

hippietrail and others added 2 commits May 23, 2026 00:49
# Conflicts:
#	harper-core/src/linting/phrase_set_corrections/mod.rs
#	harper-core/src/linting/phrase_set_corrections/tests.rs
elijah-potter
elijah-potter previously approved these changes May 27, 2026
@elijah-potter elijah-potter enabled auto-merge May 27, 2026 16:17
auto-merge was automatically disabled May 30, 2026 07:47

Head branch was pushed to by a user without write access

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants