Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CB-438: add rel=nofollow to links in reviews #461

Merged
merged 2 commits into from
Aug 30, 2022
Merged

Conversation

alastair
Copy link
Collaborator

Because we allow users to write links in reviews and comments, we should mark them as rel=nofollow so that any spam links that might come through don't negatively affect CB's search ranking

I didn't include noreferrer (or noopener) in this case, I'm not sure if it's strictly necessary as well, any thoughts @amCap1712?

Because we allow users to write links in reviews and comments, we should
mark them as rel=nofollow so that spam links don't negatively affect
CB's search ranking
@alastair alastair requested a review from amCap1712 August 24, 2022 11:38
@alastair alastair changed the title CB-438 (I): add rel=nofollow to links in reviews CB-438: add rel=nofollow to links in reviews Aug 24, 2022
@github-actions

This comment has been minimized.

Copy link
Member

@amCap1712 amCap1712 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's noopener to links as well but otherwise LGTM, Thanks!

@github-actions

This comment has been minimized.

@alastair alastair merged commit cba7523 into master Aug 30, 2022
@alastair alastair deleted the CB-438-rel-nofollow branch August 30, 2022 16:41
@github-actions
Copy link

Unit Test Results

    1 files  ±0      1 suites  ±0   2m 2s ⏱️ ±0s
196 tests ±0  196 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit cba7523. ± Comparison against base commit cba7523.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants