One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
| disabled_rules: # rule identifiers to exclude from running | |
| - trailing_whitespace | |
| - vertical_whitespace | |
| - variable_name | |
| - type_name | |
| opt_in_rules: # some rules are only opt-in | |
| # Find all the available rules by running: | |
| # swiftlint rules | |
| included: # paths to include during linting. `--path` is ignored if present. |
| ## Build generated | |
| build/ | |
| DerivedData/ | |
| ## Various settings | |
| *.pbxuser | |
| !default.pbxuser | |
| *.mode1v3 | |
| !default.mode1v3 | |
| *.mode2v3 |
| # This build phase script updates the Info.plist file of your archived Xcode project with the current build number | |
| # The build number is calculated by counting the amount of git commits on the current branch | |
| # Updating the plist file in the archive has the benefits that this won't result in a code change which then would be visible in git as uncommited change | |
| # Just set the build number in Xcode to something like "AUTO_GENERATED" in order to make clear that this value comes from somewhere else | |
| # You need to add the script after the "Copy Bundle Ressource" phase, otherwise, there wont be an archive | |
| # Ideally, just place it at the end of your build phases | |
| # If your app uses a Settings.bundle and the settings should show the app version, you can use the second part of the script to update the settings bundle |