Everyone is welcome to contribute to Swift. Contributing doesn’t just mean submitting pull requests—there are many different ways for you to get involved, including answering questions on the forums, reporting or triaging bugs, and participating in the Swift evolution process.

No matter how you want to get involved, we ask that you first learn what’s expected of anyone who participates in the project by reading the Community Overview. If you’re contributing code, you should also know how to build and run Swift from the repository, as described in Source Code.

Answering Questions

One of the most important and immediate ways you can support the community is to answer questions on the forums. Whether you’re helping a newcomer understand a language feature or troubleshooting an edge case with a seasoned developer, your knowledge and experience of Swift can go a long way to help others.

Reporting Bugs

Reporting bugs is a great way for anyone to help improve Swift. The open source Swift project uses GitHub Issues for tracking bugs.

If a bug can be reproduced only within an Xcode project or a playground, or if the bug is associated with an Apple NDA, please file a report to Apple’s bug reporter instead.

When opening an issue, please include the following:

Because Swift is under very active development, we receive a lot of bug reports. Before opening a new issue, take a moment to browse our existing issues to reduce the chance of reporting a duplicate.

Before filing an issue requesting a new language feature, see the Swift Evolution Process section.

Triaging Bugs

Reporting bugs is an important part of improving software. Nearly as important is triaging those bugs to ensure that they are reproducible, small, and unique.

There are a number of things you can do to help triage bugs in the bug tracker.

Website and Blog Post Contributions

The Swift project welcomes suggestions and enhancements to this website and community blog post contributions showcasing initiatives and stories across the community. The Swift Website Workgroup oversees all website and blog post contributions.

Learn more about contributing to this website in the website governance process and about how to submit blog post contributions.

Swift Evolution

Shaping the future of Swift is a community effort that anyone can participate in via the Evolution section of the Swift forums. The Swift evolution process covers all changes to the Swift language and the public interface of the Swift standard library, including new language features and APIs, changes to existing language features or APIs, removal of existing features, and so on.

See the Swift evolution review schedule for current and upcoming proposal reviews.

Good First Issues

Good first issues are bugs, ideas, and tasks that are intended to be accessible for contributors that are new to working on the Swift project, and even new to the patterns and concepts behind subprojects such as the Swift compiler. Good first issues are decorated with a corresponding label and are most easily found by visiting<repository>/contribute, e.g. for the main Swift repository. They are expected to be low-priority and of modest scope, and not require excessive refactoring, research, or debugging — rather, they should encourage newcomers to dip their toes in some part of Swift, learn more about it, and make a real contribution.

Anyone with commit access and insight into a particular area is welcome and encouraged to pin down or think up good first issues.

Contributing Code

Getting Started

It is highly recommended that you become familiar with using Swift in your own projects before contributing directly to the language itself. We put together handy Getting Started guides with step-by-step instructions to get you up and running.

Incremental Development

The Swift project uses small, incremental changes as its preferred development model. Sometimes these changes are small bug fixes. Other times, these changes are small steps along the path to reaching larger stated goals. In contrast, long-term development branches can leave the community without a voice during development. Some additional problems with long-term branches include:

To address these problems, Swift uses an incremental development style. Small changes are preferred whenever possible. We require contributors to follow this practice when making large or otherwise invasive changes. Some tips follow:

If you are interested in making a large change and feel unsure about its overall effect, please make sure to first discuss the change and reach a consensus through the developer forums. Then ask about the best way to go about making the change.

Commit Messages

Although we don’t enforce a strict format for commit messages, we prefer that you follow the guidelines below, which are common among open source projects. Following these guidelines helps with the review process, searching commit logs, and email formatting. At a high level, the contents of the commit message should be to convey the rationale of the change, without delving into much detail. For example, “bits were not set right” leaves the reviewer wondering about which bits and why they weren’t “right”. In contrast, “Correctly compute ‘is dependent type’ bits in ‘Type’” conveys almost all there is to the change.

Below are some guidelines about the format of the commit message itself:

For minor violations of these guidelines, the community normally favors reminding the contributor of this policy over reverting. Minor corrections and omissions can be handled by sending a reply to the commits mailing list.

Attribution of Changes

When contributors submit a change to a Swift subproject, after that change is approved, other developers with commit access may commit it for the author. When doing so, it is important to retain correct attribution of the contribution. Generally speaking, Git handles attribution automatically.

We do not want the source code to be littered with random attributions like “this code written by J. Random Hacker”, which is noisy and distracting. Do not add contributor names to the source code or documentation.

In addition, don’t commit changes authored by others unless they have submitted the change to the project or you have been authorized to submit on their behalf—for example, you work together and your company authorized you to contribute the changes. The author should first either submit the change through a pull request to the relevant project, email the development list, or add a bug tracker item. If someone sends you a change privately, encourage them to submit it to the appropriate list first.

Code Templates

As mentioned in the Community Overview, the license and copyright protections for code are called out at the top of every source code file. On the rare occasion you contribute a change that includes a new source file, ensure that the header is filled out appropriately.

For Swift source files the code header should look this:

// This source file is part of the open source project
// Copyright (c) 2024 Apple Inc. and the Swift project authors
// Licensed under Apache License v2.0 with Runtime Library Exception
// See for license information
// See for the list of Swift project authors

For C or C++ source or header files, the code header should look this:

//===-- subfolder/Filename.h - Very brief description -----------*- C++ -*-===//
// This source file is part of the open source project
// Copyright (c) 2024 Apple Inc. and the Swift project authors
// Licensed under Apache License v2.0 with Runtime Library Exception
// See for license information
// See for the list of Swift project authors
/// \file
/// This file contains stuff that I am describing here in the header and will
/// be sure to keep up to date.

The divider lines should be exactly 80 characters wide to aid in adherence to the code style guidelines. The bottom section contains an optional description intended for generated documentation (these lines begin with /// rather than //). If there is no description, this area can be skipped.

Release Branch Pull Requests

A pull request targeting a release branch (release/x.y or swift/release/x.y) cannot be merged without a GitHub approval by a corresponding branch manager. In order for a change to be considered for inclusion in a release branch, the pull request must have:

Here is an example.

Code Review

The Swift project relies heavily on code review to improve software quality:

Code review can be an iterative process, which continues until the change is ready to be committed. After a change is sent out for review it needs an explicit approval before it’s submitted. Do not assume silent approval or request active objections to the patch by setting a deadline.

Sometimes code reviews will take longer than you would hope for, especially for larger features. Here are some accepted ways to speed up review times for your patches:

Note that anyone is welcome to review and give feedback on a change, but only people with commit access to the repository can approve it.


Developers are required to create test cases for any bugs fixed and any new features added, and to contribute them along with the changes.


People depend on Swift to create their production software. This means that a bug in Swift could cause bugs in thousands, even millions of developers’ products. Because of this, the Swift project maintains a high bar for quality. The minimum quality standards that any change must satisfy before being committed to the main development branch include:

  1. Code must compile without errors or warnings on at least one platform.
  2. Bug fixes and new features must include a test case to pinpoint any future regressions, or include a justification for why a test case would be impractical.
  3. Code must pass the appropriate test suites—for example, the swift/test and swift/validation-test test suites in the Swift compiler.

Additionally, the committer is responsible for addressing any problems found in the future that the change may cause. This responsibility means that you may need to update your change in order to:

We prefer that these issues be handled before submission, but we understand that it isn’t possible to test all of this for every submission. Our continuous integration (CI) infrastructure normally finds these problems. We recommend watching the CI infrastructure throughout the next day to look for regressions. The CI infrastructure will directly email you if a group of commits that included yours caused a failure. You are expected to check those messages to see whether they are your fault and, if so, fix the breakage.

Commits that clearly violate these quality standards may be reverted, in particular when the change blocks other developers from making progress. The developer is welcome to recommit the change after the problem has been fixed.

Commit Access

Commit access is granted to contributors with a track record of submitting high-quality changes. If you would like commit access, please send an email to the code owners list with the GitHub user name that you want to use and a list of 5 non-trivial pull requests that were accepted without modifications.

Once you’ve been granted commit access, you will be able to commit to all of the GitHub repositories that host projects. To verify that your commit access works, please make a test commit (for example, change a comment or add a blank line). The following policies apply to users with commit access:

Multiple violations of these policies or a single egregious violation may cause commit access to be revoked. Even with commit access, your changes are still subject to code review. Of course, you are also encouraged to review other peoples’ changes.

Adding External Library Dependencies

There may be times where it is appropriate for one of the Swift projects (compiler, Core Libraries, etc.) to make use of libraries that provide functionality on a given platform. Adding library dependencies impacts the portability of Swift projects, and may involve legal questions as well.

As a rule, all new library dependencies must be explicitly approved by the Project lead.

LLVM and Swift

Swift is built on the LLVM Compiler Infrastructure. Swift uses the LLVM Core for code generation and optimization (among other things), Clang for interoperability with C and Objective-C, and LLDB for debugging and the REPL.

Apple maintains a fork of the LLVM Core source repository on GitHub as llvm-project, respectively. This repository track upstreams LLVM development and contains additional changes for Swift. The upstream LLVM repository are merged into the Swift-specific repository frequently. Every attempt is made to minimize the differences between upstream LLVM and the Apple fork to only those changes specifically required for Swift.

Where Do LLVM Changes Go?

Swift follows a policy of making a change in the most upstream repository that is feasible. Contributions to Swift that involve Apple’s version of LLVM Project should go directly into the upstream LLVM repository unless they are specific to Swift. For example, an improvement to LLDB’s data formatters for a Swift type belongs in the Apple LLVM Project repository, whereas a bug fix to an LLVM optimizer—even if it’s only been observed when operating on Swift-generated LLVM IR—belongs in upstream LLVM.

Commits to an upstream LLVM repository are automatically merged into the appropriate upstream branches in the corresponding Swift repository (next in the llvm-project.

Swift and LLVM Developer Policies

Contributions to Swift’s LLVM or Clang clones are governed by the LLVM Developer Policy and should follow the appropriate licensing and coding standards. Issues with LLVM code are tracked using the LLVM bug database. For LLDB, changes to files with comment headers must go to the upstream LLDB at and abide by the LLVM Developer Policy and LLDB coding conventions. Contributions to the Swift-specific parts of LLDB (that is, those with a comment header) use the Swift license but still follow the LLDB coding conventions.