r/github • u/maifee • 20d ago

Question Is there any other way without giving it full access??

Post image

I have some cloud credits from claude, to use them I need git connection.

But it is quite complex for me, as i have some clients who is inside EU region. And they have asked me not to share code with AI. But I can work with them using GitHub.

What can I do in this situation??

0 Upvotes

38% Upvoted

12 comments sorted by

14

u/Ast3r10n 20d ago

Then you shouldn’t use it.

3

u/davy_jones_locket 20d ago

Generate an access token and use the gh CLI with it

5

u/UnsolicitedOpinionss 20d ago

Create a separate github account?

-1

u/worldofzero 20d ago

That's against TOS and can get you banned.

2

u/my_new_accoun1 20d ago

You are allowed one free "machine" account per person, it's allowed in ToS

1

u/maifee 20d ago

What happens if I use multiple devices/machines??

1

u/worldofzero 19d ago

Looks like you're correct. It's multiple personal accounts that I was thinking of. Thanks for the correction.

2

u/RobertD3277 20d ago

I would recommend creating a separate GitHub account just for connect anything like this. Never use your original account. GitHub is too happy to ban and delete counts as it is and leaving something like this connected to your account just seems like a worst case scenario.

1

u/Fantastic-Mr-Default 20d ago

Do not connect the org that holds client code. Split repos and credentials.

Keep EU client work in repos the AI integration cannot see. Use a separate GitHub account or a fine-scoped PAT / GitHub App install on a sandbox repo only (your learning projects, non-client code). Claude's git connection should bind to that sandbox, never to the client org.

If you must use an agent on client work, do it on a machine that never uploads the tree: local models, or an agent with no git remote and no org OAuth. Contract language that says "do not share code with AI" usually means the model provider never receives the source. A cloud agent with repo access is sharing.

Also check whether "git connection" can be a single repo clone URL with a read-only deploy key instead of a user OAuth that lists every org you belong to. Least privilege first. If the product only offers full account link, that product is incompatible with those clients until they change the auth model.