<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitfence blog</title><link>https://gitfence.dev/blog/</link><description>Repository access control for people and AI agents.</description><language>en</language>
<atom:link href="https://gitfence.dev/blog/rss.xml" rel="self" type="application/rss+xml"/>
<lastBuildDate>Fri, 09 Oct 2026 12:00:00 GMT</lastBuildDate>
<item><title>Can You Restrict Access to Folders in a GitHub Repo?</title><link>https://gitfence.dev/blog/restrict-access-to-folders-in-github-repository/</link><guid isPermaLink="true">https://gitfence.dev/blog/restrict-access-to-folders-in-github-repository/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>github permissions</category><category>folder permissions</category><category>access control</category></item>
<item><title>CODEOWNERS Is Not Access Control (What It Actually Does)</title><link>https://gitfence.dev/blog/codeowners-is-not-access-control/</link><guid isPermaLink="true">https://gitfence.dev/blog/codeowners-is-not-access-control/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>codeowners</category><category>github</category><category>branch protection</category><category>access control</category></item>
<item><title>Git Sparse Checkout vs Real Access Control</title><link>https://gitfence.dev/blog/git-sparse-checkout-vs-access-control/</link><guid isPermaLink="true">https://gitfence.dev/blog/git-sparse-checkout-vs-access-control/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>git</category><category>sparse checkout</category><category>partial clone</category><category>access control</category></item>
<item><title>How to Give Contractors Access to Part of a GitHub Repo</title><link>https://gitfence.dev/blog/give-contractors-access-to-part-of-github-repo/</link><guid isPermaLink="true">https://gitfence.dev/blog/give-contractors-access-to-part-of-github-repo/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>contractors</category><category>github permissions</category><category>access control</category></item>
<item><title>Least-Privilege Repo Access for Claude Code, Codex, Cursor</title><link>https://gitfence.dev/blog/least-privilege-repo-access-ai-coding-agents/</link><guid isPermaLink="true">https://gitfence.dev/blog/least-privilege-repo-access-ai-coding-agents/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>How to give Claude Code, Codex and Cursor least-privilege repository access with permission rules, sandboxes, scoped tokens and filtered clones.</description><category>ai agents</category><category>claude code</category><category>codex</category><category>cursor</category><category>least privilege</category><category>mcp</category></item>
<item><title>Monorepo Permissions for Per-Team Access in One Repo</title><link>https://gitfence.dev/blog/monorepo-permissions-per-team-access/</link><guid isPermaLink="true">https://gitfence.dev/blog/monorepo-permissions-per-team-access/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>monorepo</category><category>permissions</category><category>access control</category><category>codeowners</category></item>
<item><title>NDAs for Developers Before Code Access (Practical Guide)</title><link>https://gitfence.dev/blog/nda-for-developers-before-code-access/</link><guid isPermaLink="true">https://gitfence.dev/blog/nda-for-developers-before-code-access/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>nda</category><category>contractors</category><category>onboarding</category><category>source code protection</category></item>
<item><title>Onboarding New Developers Without Full Codebase Access</title><link>https://gitfence.dev/blog/onboard-new-developers-without-full-codebase-access/</link><guid isPermaLink="true">https://gitfence.dev/blog/onboard-new-developers-without-full-codebase-access/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>onboarding</category><category>new hires</category><category>least privilege</category><category>access control</category></item>
<item><title>Protecting Source Code from AI Agents and Contractors</title><link>https://gitfence.dev/blog/protect-source-code-from-ai-coding-agents/</link><guid isPermaLink="true">https://gitfence.dev/blog/protect-source-code-from-ai-coding-agents/</guid><pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate><description>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.</description><category>ai agents</category><category>contractors</category><category>source code protection</category><category>ip protection</category></item>
</channel></rss>
