Reflexion sobre el futuro (Spanish version)

Jose Juan MontielJose Juan Montiel

And after all that reflection, time passed again and…​

and I had to keep updating all these reflections, because once you do something, and it works, why not keep doing it?

And the thing is, all of this included several hidden games, one of which was the hidden CV, which, by the way, after using "git filter-branch" and reviewing it these past few days, doesn’t seem to be working as expected. But, as you learn from everything over time, it’s already been resolved.

And what happened? Well, one of the lines in this review (resume) of things I had done years ago (almost 7 years ago as of this writing) was a security vulnerability, or so they said. The thing is…​ imagine you have to make a word or phrase, or even lines from your repository, including old versions, disappear from Git because they’re a security vulnerability. "git filter-repo" to the rescue!

git filter-repo --commit-callback '
    commit.committer_date = commit.author_date
' --force --replace-text replace.txt

git remote add origin https://github.com/josejuanmontiel/josejuanmontiel.github.io.git
git push -u origin main

And also, with those lines you maintain the original commit date, although of course the hash will change because it will be a new repo.

El TEXTO ... ==>
siguiente linea ==>
ultima linea ==> Nuevo texto que no es una brecha de seguridad

Why do we organize the replacement file this way? According to the documentation…​

--replace-text <expressions_file>
        A file with expressions that, if found, will be replaced. By default, each expression is treated as literal text, but regex: and glob:
        prefixes are supported. You can end the line with ==> and some replacement text to choose a replacement choice other than the default
        of ***REMOVED***.

The thing is, it works line by line, so we have to put a space for each line that’s part of what we want to replace. If we put the line without the space, leaving the line break and thinking it would work, it would just show REMOVED. So, as I said, each line is replaced with empty space (or something similar), and the final line contains the new result we want.

Here’s a summary of the links:

Note: As a final note, note that rebasing in this case does not achieve the objective. If the origin of what you want to change is very far down, you have to manually change many commits and it can be tedious. Besides, then with the branch, you would have to generate another git file exporting only that branch…​ or something like that.

Extra: With

git grep TEXTO $(git rev-list --all)

We can search for a text in all commits, and if we do

git filter-repo --invert-paths --path resources/cv/CV_JOSE_JUAN_MONTIEL-2022-Marzo.odt --force

we can delete the file from the repository.