git-verify-tag: add page

[CleanMachine1]

• The page (if new), does not already exist in the repo.
• The page is in the correct platform directory (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.
• The page description includes a link to documentation or a homepage (if applicable).

For #3953

[CleanMachine1]

Make sure to take a look at #5946

[CleanMachine1]

Also the Gitter section, I have left some more comments

[CleanMachine1]

Thought it was ironic that the verify-tag page wasn't signed, since my key was removed. So I rebased and squashed and signed it

[bl-ue]

(Sorry, I just wanted to test the locking feature 😄 — turns out even collaborators can't react/unreact 🤔)
(also, that says "bl-ue locked" to us, but to a non-collaborator it would say "tldr-pages locked")

[CleanMachine1]

That should probably be changed to give the option

[sbrl]

The idea there @CleanMachine1 is that by saying tldr-pages locked, it avoids publicly naming the person who locked the thread. This is important in heated situations because otherewise the person doing the locking may be targeted on other platforms and the conversation might just continue anyway. That way they allow everyone some cooling off time.

Thankfully we've never had a need to use that feature haha

[sbrl]

Looks ok to me after @marchersimon's comment is addressed.

[bl-ue]

the person doing the locking may be targeted on other platforms

Often though, the one doing the locking says "I'm going to lock this now" or something similar before doing it 😉

[marchersimon]

👍🏽

[CleanMachine1]

• Bl-ue's approval makes it 3