Only Googlebot can access doi.org

bklaing2 commented 1 month ago

Purpose

closes: Add github issue that originated this PR

Approach

Open Questions and Pre-Merge TODOs

Learning

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

Be humble in the language and feedback you give, ask don't tell.
Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
Offer suggestions on how to improve code e.g. simplification or expanding clarity.
Ensure you give reasons for the changes you are proposing.

cypress[bot] commented 1 month ago

3 flaky tests on run #1222 ↗︎

0

55

0

3

Details:

Merge cfde3bcab2c29b498e37ce579ebf1c952cdd4b05 into d48793de341c8380cb1ad5bb8122...
Project: akita	Commit: `1335fbc958 ℹ️`
Status: Passed	Duration: 02:49 💡
Started: May 31, 2024 12:36 PM	Ended: May 31, 2024 12:39 PM

statistics.test.ts • 1 flaky test • Tests

View Output

Test		Artifacts
Overview > header		`Test Replay` `Screenshots`

fundrefContainer.test.ts • 2 flaky tests • Tests

View Output

Test		Artifacts
FundrefContainer > id		`Test Replay` `Screenshots`
FundrefContainer > not in ror		`Test Replay` `Screenshots`

Review all test suite changes for PR #362 ↗︎

richardhallett commented 7 hours ago

Apologies I missed this PR and did the same: https://github.com/datacite/akita/pull/369 They are functionally equivalent although I do not explicitly deny adbot, but this is covered by the global ignore.

datacite / akita

Only Googlebot can access doi.org #362