Problem/Motivation

Fastly is verifying my browser all the time, ok it makes drupal. org happy, I can live with that.

However, I just tried to review a MR on gitlab and it swallowed my comments. During devdays we agreed that thid was probably because the ajax request was eaten by the check.
This leads to review comments being lost and that is very frustrating.

Steps to reproduce

Carefully review a big MR taking enough time to hit the timeout for a re-verification.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

bircher created an issue. See original summary.

andypost’s picture

Maybe it makes sense to increase timeout as it slows down any Gitlab navigation

drumm’s picture

Title: Allow reviewing MRs on gitlab » Bypass browser verification for logged in users
Assigned: Unassigned » drumm
dww’s picture

This happened to me yesterday, too. And I wasn’t even at Devdays. 😂 Would be great not to keep reverifying authenticated traffic. Thanks!

xjm’s picture

This happened to me repeatedly over the past two days as well. I don't even know some of the review comments that I lost.

xjm’s picture

Issue tags: +DevDaysAthens2026
drumm’s picture

Status: Active » Needs review

This is now set up for drupalcode.org. If you do not switch IPs or browsers, you should not see “Checking your browser” again for up to a month.

Next is setting this up for *.Drupal.org sites.

drumm’s picture

drumm’s picture

Status: Needs review » Fixed

This is now active for *.drupal.org sites. The other requirement for this to remain active for any individual is to not block cookies.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

wim leers’s picture

However, I just tried to review a MR on gitlab and it swallowed my comments.

Same here, multiple times. Both on GitLab and d.o itself.

Thanks for this lovely news, @drummm!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.