Ignore InternalAffairs/CreateEmptyFile in #create_empty_file

[r7kamura]

This is in response to the following change:

• Add new InternalAffairs/CreateEmptyFile cop rubocop#11109

This repository refers to rubocop/rubocop on GitHub and does not stage Gemfile.lock in Git index, so if a cop that detects offenses to existing code is added on rubocop gem side, the CI on rubocop-rails gem side will start to fail from that point on.

rubocop-rails/Gemfile

Line 12 in f913bb5

gem 'rubocop', github: 'rubocop/rubocop'

I ran into this problem when I created the following Pull Request, so I decided to create this Pull Request too.

• Add Rails/SpecificActionNames cop #827
• https://app.circleci.com/pipelines/github/rubocop/rubocop-rails/2069/workflows/84921743-0ec3-45af-aea8-ef00aa7d85e6/jobs/13915

---

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.
• If this is a new cop, consider making a corresponding update to the Rails Style Guide.

[r7kamura]

I think it is preferable to deal with it this way for the time being to solve the current problem. However, in the future, it may be better to solve this problem by providing FileHelper from rubocop gem and remove the similar implementation from rubocop-rails side.

[koic]

it may be better to solve this problem by providing FileHelper from rubocop gem and remove the similar implementation from rubocop-rails side.

Yep, I think so too.