Automattic / Automattic/harper

Should correct "get access at" to "get access to"

Open
#3,309 2 comments 0 reactions 1 assignee Claimed by @favzqn View on GitHub
enhancement good first issue grammar harper-core linting
Dominant language
Rust
Stars
15.4k
Forks
627
Avg merge
1d 15h
Merged PRs (30d)
102

Description

I just heard this in a retrocomputing YouTube video by a native speaker:

- they really need to tabulate that spreadsheet and and they need to **get access at** some CPU time.

Even though I'd never heard this one before it's out there on GitHub:
- To **get access at** the original request within the hooks, use http middleware to inject the body and pass it around with a request context.
- Succeeded to **get access at** host system with login command ?
- ... and if someone manages to **get access at** the preferences, at least it's going to be a bit more difficult to decrypt.
- in order to **get access at models**, you typically send information to some server that runs the model and response is sent back.

There are also common false positives if this were to be implemented naïvely:
- But anyway, i don't manage to **get access at all**, so i will go another way now and try to download it all as zip from a server into the app's files folder.
- **Getting access at** the /dev/disk2 level would not normally be called a mount of /dev/disk2 that I'm aware of.
- Is it possible to **get access at least** to: file_content_type, file_size and name?
- **Get access at** getpara.com.
- **Get Access at** https://developer.bitping.com.
- Contact us to **get access at** https://tanker.io/contact.
- **get access at** https://github.com/malaysia-ai/label-studio#how-to-get-access
- Eventually we will stop using this but the quickest method **to get access at this time** would be to fill out this form.
- Today I **got access at least** to the nucleo_f767zi and I am trying the latest main branch.

It also looks like there are ambiguous cases that make sense with both "at" and "to":
- but if I set in the client "Authentication=Anonymous" still I can **got access at** server without any Username/Password!!

I also saw this one twice, which seems to be a different nonnative speaker mistake for "**can be accessed at**":
- The license text in full can be **getting access at** the file named COPYING-GPL-3.0.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.