fix: set up configs

.github/CODEOWNERS

@@ -3,4 +3,4 @@
 # @org/team will be requested for review when someone opens
 # a pull request. Order is important; the last matching
 # pattern takes the most precedence.
-#*                    @org/team
+#*                    @mytiki/frontend

.github/settings.yml

@@ -2,58 +2,39 @@
 
 _extends: .github
 
-#repository:
-#  # The name of the repository. Changing this will rename the repository
-#  name: repo-name
-#
-#  # A short description of the repository that will show up on GitHub
-#  description: description of repo
-#
-#  # A URL with more information about the repository
-#  homepage: https://example.github.io/
-#
-#  # A comma-separated list of topics to set on the repository
-#  topics: github, probot
-#
-#  # Either `true` to make the repository private, or `false` to make it public.
-#  private: false
-
-#teams:
-#  - name: core
-#    permission: admin
-
-#collaborators:
-#  - username: bkeepers
-#    permission: push
-
-# The permission to grant:
-# * `pull` - can pull, but not push to or administer this repository.
-# * `push` - can pull and push, but not administer this repository.
-# * `admin` - can pull, push and administer this repository.
-# * `maintain` - Recommended for project managers who need to manage the repository without access to sensitive or destructive actions.
-# * `triage` - Recommended for contributors who need to proactively manage issues and pull requests without write access.
-
-#environments:
-#  - name: production
-#    reviewers:
-#      - id: 1
-#        type: 'Team'
-
-#branches:
-#  - name: main
-#    protection:
-#      required_status_checks:
-#        strict: true
-#        # Required. The list of status checks to require in order to merge into this branch
-#        contexts: []
-
-#labels:
-#  - name: breaking
-#    color: D73A4A
-#    description: Introduces a breaking change.
-
-#milestones:
-#  - title: milestone-title
-#    description: milestone-description
-#    # The state of the milestone. Either `open` or `closed`
-#    state: open
+repository:
+  name: client-library-ios
+  description: integrate your iOS app with mytiki.com
+  homepage: https://docs.mytiki.com/reference/client-library-overview
+  topics: iOS, library
+  private: false
+
+teams:
+  - name: sysadmin
+    permission: admin
+  - name: engineering
+    permission: push
+  - name: product
+    permission: triage
+  - name: frontend
+    permission: push
+
+environments:
+  - name: production
+
+branches:
+  - name: main
+    protection:
+      required_status_checks:
+        strict: true
+        contexts:
+          - Test
+          - CodeQL
+
+milestones:
+  - title: 0.3.0
+    description: |
+      Adds support for intelligent email scraping of e-receipts. Emails are fetched using a pre-qualified list
+      of known receipt senders and parsed locally to the mobile device to protect privacy. Emails are eagerly fetched
+      starting with the most recent and working progressively in reverse chronological order when time-permitted.
+    state: open

.github/workflows/codeql.yml

@@ -43,7 +43,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        include:
+        include: swift
         # CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
         # Use `c-cpp` to analyze code written in C, C++ or both
         # Use 'java-kotlin' to analyze code written in Java, Kotlin or both