<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Gitfence blog</title><subtitle>Repository access control for people and AI agents.</subtitle>
<link href="https://gitfence.dev/blog/atom.xml" rel="self"/><link href="https://gitfence.dev/blog/"/><id>https://gitfence.dev/blog/</id><updated>2026-10-09T12:00:00Z</updated>
<entry><title>Can You Restrict Access to Folders in a GitHub Repo?</title><link href="https://gitfence.dev/blog/restrict-access-to-folders-in-github-repository/"/><id>https://gitfence.dev/blog/restrict-access-to-folders-in-github-repository/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>No, GitHub has no folder-level read permissions. Here&apos;s why, what GitHub does offer (CODEOWNERS, push rulesets), and the options that hide folders.</summary></entry>
<entry><title>CODEOWNERS Is Not Access Control (What It Actually Does)</title><link href="https://gitfence.dev/blog/codeowners-is-not-access-control/"/><id>https://gitfence.dev/blog/codeowners-is-not-access-control/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>GitHub CODEOWNERS requests reviews and can require approvals, but it doesn&apos;t stop anyone reading or cloning code. What it does, what it doesn&apos;t, and fixes.</summary></entry>
<entry><title>Git Sparse Checkout vs Real Access Control</title><link href="https://gitfence.dev/blog/git-sparse-checkout-vs-access-control/"/><id>https://gitfence.dev/blog/git-sparse-checkout-vs-access-control/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>Git sparse checkout hides files from your working tree, not your clone. What it does, how to bypass it in one command, and what restricts access.</summary></entry>
<entry><title>How to Give Contractors Access to Part of a GitHub Repo</title><link href="https://gitfence.dev/blog/give-contractors-access-to-part-of-github-repo/"/><id>https://gitfence.dev/blog/give-contractors-access-to-part-of-github-repo/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>GitHub grants access per repository, not per folder. Here are the real options for giving a contractor part of a repo, with commands and tradeoffs.</summary></entry>
<entry><title>Least-Privilege Repo Access for Claude Code, Codex, Cursor</title><link href="https://gitfence.dev/blog/least-privilege-repo-access-ai-coding-agents/"/><id>https://gitfence.dev/blog/least-privilege-repo-access-ai-coding-agents/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>How to give Claude Code, Codex and Cursor least-privilege repository access with permission rules, sandboxes, scoped tokens and filtered clones.</summary></entry>
<entry><title>Monorepo Permissions for Per-Team Access in One Repo</title><link href="https://gitfence.dev/blog/monorepo-permissions-per-team-access/"/><id>https://gitfence.dev/blog/monorepo-permissions-per-team-access/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>Git and GitHub have no per-folder read permissions, so how do teams restrict access inside a monorepo? Options, tradeoffs and configs for per-team access.</summary></entry>
<entry><title>NDAs for Developers Before Code Access (Practical Guide)</title><link href="https://gitfence.dev/blog/nda-for-developers-before-code-access/"/><id>https://gitfence.dev/blog/nda-for-developers-before-code-access/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>When and how to get an NDA signed before a developer or contractor sees your code, what to cover for AI tools, and how to gate access on it.</summary></entry>
<entry><title>Onboarding New Developers Without Full Codebase Access</title><link href="https://gitfence.dev/blog/onboard-new-developers-without-full-codebase-access/"/><id>https://gitfence.dev/blog/onboard-new-developers-without-full-codebase-access/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>How to onboard new hires with least-privilege codebase access so they ship in week one without a full clone. Options, tradeoffs and a day-one checklist.</summary></entry>
<entry><title>Protecting Source Code from AI Agents and Contractors</title><link href="https://gitfence.dev/blog/protect-source-code-from-ai-coding-agents/"/><id>https://gitfence.dev/blog/protect-source-code-from-ai-coding-agents/</id><published>2026-10-09T12:00:00Z</published><updated>2026-10-09T12:00:00Z</updated><author><name>Gitfence team</name></author><summary>How to protect source code when AI coding agents and contractors work in your repo, what ignore files and NDAs really do, and what limits access.</summary></entry>
</feed>
