pnpm’s offline capabilities are a direct consequence of its content-addressable store architecture. Every package file that pnpm has ever downloaded is stored once in a global directory. When you run pnpm install –offline, pnpm does not contact the registry. It resolves the dependency tree from the lockfile, locates the required files in the store, and…
A monorepo with ten workspaces requires orchestration. Running pnpm test in each workspace manually is tedious. Running it in every workspace simultaneously overloads the machine. The –filter flag selects which workspaces to target, and the –parallel and –workspace-concurrency flags control how many run at once. The filter syntax is more than a simple name matcher—it…
A monorepo stores multiple packages in a single repository. pnpm Workspaces is the mechanism that makes this practical: it installs all packages’ dependencies together into a single virtual store, links packages to each other without publishing to a registry, and provides commands to run scripts across the entire project. The architecture is defined by a…
A project’s package.json is both a manifest and a command registry. The scripts field defines named commands that can be invoked with a short alias, and pnpm provides a resolution layer that decides whether a given name refers to a script, a taskfile, or a binary from a dependency. In pnpm, the run keyword is…
The previous chapters established how pnpm links packages from a global store and constructs a virtual store. This chapter explains the consequence: a strictly isolated node_modules layout that forbids access to undeclared dependencies. npm and Yarn Classic hoist packages to the root, allowing a project to import anything in the tree. pnpm’s default behavior is…
1. Authentication (gh) 2. Repositories 3. Issues & Pull Requests 4. GitHub Actions (gh) 5. Releases 6. Git: Commits, Tags, Remotes 7. Git: Merging Strategies 8. CODEOWNERS & Branch Protection 9. Workflow Configuration (.github/workflows/ci.yml) 10. GitHub Packages (GHCR) 11. Security & Dependabot 12. GitHub Pages & Custom Domains 13. .github Directory Layout
GitHub Copilot is no longer a single autocomplete tool. It is a suite of AI-powered features spanning inline code suggestions, chat interfaces in the IDE and on GitHub.com, automated code review, and agent-based workflows that can plan and execute multi-step tasks. The LFCS/GitHub exam tests the conceptual model: what Copilot is, how it integrates into…
The GitHub CLI (gh) is the official command-line interface for GitHub. It brings the platform’s core operations—repositories, issues, pull requests, Actions, releases—into the terminal, where they can be scripted, aliased, and composed. For the exam, the critical distinction is between gh and git: git manages the local repository and its history; gh manages the GitHub…
An organization is a shared account where businesses and open-source projects manage many repositories at once. It is not a user account and it does not own code directly—it owns repositories, and access to those repositories is granted to people and teams through a layered permission model. The LFCS/GitHub exam tests this hierarchy: organization roles…
GitHub provides two distinct static analysis security features: Secret Scanning, which detects leaked credentials in code and text, and CodeQL Analysis, which performs semantic code analysis to find vulnerabilities like SQL injection or cross-site scripting. A critical change occurred in May 2025: CodeQL no longer detects hardcoded secrets. Secret Scanning is now the sole mechanism…