# Xcode 16 Published articles for Xcode 16. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Stop Using Groups in Xcode DevFeed: [Stop Using Groups in Xcode]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2025-12-07T13:07:57Z Content type: article Language: en Sources: [Mobile App Development Publication]() Topics: [Xcode](), [legacy systems]() Tags: [apple](), [coding](), [developers](), [directory](), [documentation](), [file](), [files](), [groups](), [ios](), [ios-development](), [legacy](), [mobile-app-development](), [navigator](), [project](), [projects](), [reference](), [structure](), [xcode](), [xcode-16]() ### AI overview For projects created before Xcode 16, developers can manage files with either Groups or Folders; new projects use Folders by default. The excerpt says Groups let the structure shown in Xcode differ from the on-disk directory structure or reference files outside the project. It introduces Folders as displaying folders in the Project navigator, then recommends replacing Groups in legacy projects, but cuts off before explaining the seven reasons. ### Source excerpt Seven Reasons Folders Are Better -- Especially for Legacy Projects Continue reading on Mobile App Development Publication " ## Format Swift with a Git Commit Hook DevFeed: [Format Swift with a Git Commit Hook]() Original publisher: [Read original article]() Author: Keith Harrison Published: 2025-11-24T10:29:58Z Content type: tutorial Language: en Sources: [K. Harrison]() Topics: [Swift](), [Git](), [hooks](), [software-development]() Tags: [actions](), [auto-layout](), [automatically](), [changes](), [code](), [code-style](), [commit](), [configuration](), [configure](), [custom](), [directory](), [dump](), [external](), [file](), [files](), [format](), [formatting](), [git](), [git-commit](), [ios](), [objective-c](), [swift](), [with](), [wwdc](), [xcode](), [xcode-16]() ### AI overview Xcode 16 includes `swift-format`; it runs from the active Xcode toolchain, which may be a beta or release. Formatting can use a `.swift-format` file found beside the source files or in a parent directory, falling back to defaults; a project-level file can override a shared configuration. The described pre-commit hook selects staged Swift files with Git's cached diff, formats them in place, and stages the changed files again. A nonzero exit cancels the commit. Because it is a client-side hook, it must be installed for each new or cloned repository. The excerpt notes that the hook can be bypassed with a flag but does not show which flag or the complete script. ### Source excerpt How do you automatically format your Swift code every time you commit it to your Git repository? Swift Format There are several Swift formatting tools. Xcode 16 shipped with swift-format included in the toolchain: $ xcrun --find swift-format /Applications/Xcode.app/Contents/Developer/Toolchains/ XcodeDefault.xctoolchain/usr/bin/swift-format To run the formatter: $ swift format MyFile.swift Note: This runs the swift-format bundled with the active Xcode development directory (beta or release). Configuring swift-format The Xcode settings let you configure various formatting options including indentation but I prefer to use an external configuration file for swift-format. By default, swift-format looks for a configuration file named .swift-format in the same directory as the files you are formatting. If there isn't one it looks in each successive parent directory. If it doesn't find a configuration file it uses a default configuration. You can dump the default configuration to get started: $ swift format dump-configuration > swift-format Modify the configuration file to meet your own code style: { "fileScopedDeclarationPrivacy" : { "accessLevel" : "private" }, "indentConditionalCompilationBlocks" : true, "indentSwitchCaseLabels" : false, "indentation" : { ... I keep my default configuration file in my base Developer directory: $ mv swift-format ~\Developer\.swift-format When needed, I can override the defaults by placing a modified configuration file in the project-specific root directory. Note: Don't forget to prefix the configuration file with a . Git Commit Hooks Git Hooks are a way to run custom scripts when different Git actions occur. A pre-commit hook runs when you commit changes to a repository. Here's the pre-commit script I'm using to run swift-format: #!/bin/bash GIT=/usr/bin/git GREP=/usr/bin/grep SWIFT=/usr/bin/swift # Staged (cached) added/copied/modified/renamed files FILES=$($GIT diff --cached --name-only --diff-filter=ACMR | $GREP '\.swift$') # Exit ear ## Actions: Xcode 16.2 will replace Xcode 16.0 in macOS-14 Images DevFeed: [Actions: Xcode 16.2 will replace Xcode 16.0 in macOS-14 Images]() Original publisher: [Read original article]() Author: Allison Published: 2025-01-02T18:08:17Z Content type: release Language: en Sources: [GitHub Changelog]() Topics: [macOS](), [Xcode](), [GitHub]() Tags: [2025](), [actions](), [all](), [arm64](), [beta](), [github](), [github-actions](), [images](), [intel](), [macos](), [policy](), [roadmap](), [runner](), [service](), [support](), [tools](), [upgrade](), [version](), [xcode](), [xcode-16]() ### AI overview Starting January 6, 2025, GitHub-hosted macOS-14 Intel and ARM64 runner images will replace Xcode 16.0 with Xcode 16.2. Workflows that rely on Xcode 16.0 should upgrade to Xcode 16.1 to maintain service continuity. The stated macOS-14 support policy keeps all Xcode 15 minor releases with the full platform tools suite, while Xcode 16 follows a "last two" policy: two minor releases are supported, excluding visionOS tools, and the oldest is replaced as updates are released. Beta versions are excluded. ### Source excerpt Starting January 6, 2025 GitHub-Hosted macOS runner images will be replacing Xcode 16.0 with Xcode 16.2. This change applies to both macOS-14 Intel and ARM64 based runner images. If you...