Approve+merge of #332 was blocked by the permission classifier, so nothing happened yet. Allow it (or merge it yourself) and tell me; I'll retry with your apology in the approval. @dtinth
Approved #332 with your apology, but the merge failed: conflict with #331 (both append at the end of the list). Maintainer edits are allowed, so I can merge main into their branch and push, then merge. Do that, or ask them to rebase? @dtinth
Merged main into #332 locally and resolved the conflict (keeps both entries). Pushing to the contributor's fork branch was blocked by the permission classifier, so nothing is pushed. Allow the push? @dtinth
Please also fix the merge conflict on that PR. So when you start looking at a PR, please get it up to date against the latest main before triggering a review.
Resolved the #333 conflict locally (keeps all three entries), but pushing to the contributor's fork was blocked again by the permission classifier. Please allow it; I'll then push and trigger the review. @dtinth
#333 suthee.space is now up to date with main (pushed a merge, conflict fixed) and mergeable. Review re-triggered; a validation comment exists (backlink found), the new run is still pending. Site is a personal portfolio on its own domain. Check the icon. https://suthee.space…
Approve+merge of #333 was blocked by the permission classifier again, so nothing happened. Please allow it (or a standing rule for gh pr review/merge) and tell me. @dtinth
Can't add the standing rule myself: the classifier blocks me editing my own permission settings. Rules are in the terminal for you to paste into ~/.claude/settings.json. #333 is still unmerged; allow it via /permissions and I'll proceed. @dtinth
You can fix them. I've verified that the icon appears on the website. I also verified that the website has a link to the GitHub profile and it matches the username of the PR opener.
Fixed #335 on their branch: data-owner is now Vinniel5403 (and indentation). Pushed, mergeable, Netlify passes. Approve with your apology and squash-merge? @dtinth
Two open issues, no comments on either. #183 (Oct 2023, veer66): where to paste the badge HTML on wordpress.com; also veer66.wordpress.com isn't an own domain. #44 (2021, yours): native prev/random/list link suffix idea. Reply to #183 with the domain rule? @dtinth
We want to be helpful to others who stumble upon the issue too. So, let's discuss first.
I want to know, on a wordpress.com site, assuming that you have the custom domain, how would you put a web link icon on there?
Per WordPress.com docs, the Custom HTML block allows <a> and <img> on all plans (script/iframe need a paid plan with a plugin). Docs say it goes in a page, post or template, so footer = edit the footer template in the Site Editor. I haven't tested the UI. Want the full write-up?…