Update from Hummingbird Project Template

.github/workflows/ci.yml

@@ -13,9 +13,21 @@ concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}-ci
   cancel-in-progress: true
 
-env:
-  ENABLE_HB_BENCHMARKS: true
 jobs:
+  macOS:
+    runs-on: macos-26
+    timeout-minutes: 15
+    steps:
+    - name: Select appropriate Xcode version
+      uses: maxim-lobanov/setup-xcode@v1
+      with:
+        xcode-version: latest-stable
+    - name: Checkout
+      uses: actions/checkout@v6
+    - name: Build
+      run: |
+        swift build
+
   linux:
     runs-on: ubuntu-latest
     timeout-minutes: 15
@@ -24,13 +36,16 @@ jobs:
         image: ["swift:6.0", "swift:6.1", "swift:6.2"]
     container:
       image: ${{ matrix.image }}
+    env:
+      ENABLE_HB_BENCHMARKS: true
     steps:
     - name: Checkout
       uses: actions/checkout@v6
     - name: Install libjemalloc-dev
       run: |
         apt-get -q update
         apt-get install -y libjemalloc-dev
+
     - name: Test
       run: |
         swift test --enable-code-coverage

.github/workflows/nightly.yml

@@ -12,9 +12,16 @@ jobs:
         image: ['nightly-focal', 'nightly-jammy', 'nightly-amazonlinux2']
     container:
       image: swiftlang/swift:${{ matrix.image }}
+    env:
+      ENABLE_HB_BENCHMARKS: true
     steps:
     - name: Checkout
       uses: actions/checkout@v6
+    - name: Install libjemalloc-dev
+      run: |
+        apt-get -q update
+        apt-get install -y libjemalloc-dev
+
     - name: Test
       run: |
         swift test

CONTRIBUTING.md

@@ -15,18 +15,20 @@ Please ensure to include the following in your bug report
 - Contextual information (Swift version, OS etc)
 
 ## Adding a Feature
-Prior to adding features to Hummingbird, please discuss the feature request in an issue and/or on our Discord server. That way we can shape the new feature together, make it fit the project, and validate it's within our vision of the framework.
+Prior to adding features please discuss the feature request in an issue and/or on our Discord server. That way we can shape the new feature together, make it fit the project, and validate it's within our vision of the framework.
 
 ## Submitting a Pull Request
+
 Please ensure to include the following in your Pull Request
 - A link referencing the issue (bug or feature request) it fixes
 - A description of the code changes
 - Documentation on how these changes are being tested
 - Additional tests to show your code working and to ensure future changes don't break your code.
 
-Please keep your PRs to a minimal number of changes, this helps us review and merge it timely. If a PR is large try to split it up into smaller PRs. Don't move code around unnecessarily as it makes comparing old with new very hard.
+Please keep your PRs to a minimal number of changes. This helps us review and merge them in a timely fashion. If a PR is large try to split it up into smaller PRs. Don't move code around unnecessarily as it makes comparing old with new very hard.
 
 The main development branch of the repository is  `main`.
 
 ### Formatting
-We use Apple's swift-format for formatting code. PRs will not be accepted until they're formatted.
+
+We use Apple's swift-format for formatting code. PRs will not be accepted if they haven't be formatted.

LICENSE.txt

@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2021 Adam Fowler
+   Copyright [yyyy] [name of copyright owner]
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.