Why is the problem URL still available after using `git filter-repo` to handle a GitHub DMCA takedown notice?

Git
, , , ,
1

How did I remove the Amasty folder from my Git repositories history following a DMCA takedown notice?

A GitHub user received a DMCA takedown notice regarding content in their repository:

I'm contacting you on behalf of GitHub because we've received a DMCA takedown notice regarding the following content:
https://github.com/<…>

The DMCA notice states:

Once you've made the requested changes, please let us know by responding to this email so we can let the complainant know the requested changes have been made. If we don't hear from you, we will re-disable your repository in 1 business day.

The user correctly performed the following actions to remove the problematic content:

git clone <…> .
cp ./.git/config ../
git filter-repo --invert-paths --path app/code/Amasty
mv -f ../config ./.git
git push --force --all
git push origin --force --tags

After this, they submitted a "clear cached views" request through GitHub's support form at:

The problematic URL remained accessible, displaying the message:
«This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.»

2

This is completely normal because:

  1. GitHub needs some time to process cached data removal requests.
  2. The error message confirms that:
    2.1) The commit is no longer part of your current repository history.
    2.2) It just temporarily remains in GitHub's system cache.

Important:

  1. You must respond to the DMCA notice within 1 business day, even if the problematic URL is still visible in cached views.
  2. GitHub will create a support ticket for your cached views cleanup request.
  3. In your response to the DMCA notice, you should:
    3.1) Confirm you have removed the content.
    3.2) Reference your cached views cleanup request ticket number.

Here is a template for your response to the DMCA notice:

  1. I have removed the problem content from my GitHub repository.
  2. I have submitted a request to GitHub support to clear cached views (ticket #).
    `