Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/nef10/common-swift-package
Repo which holds and syncs files which are shared between my swift packages
https://github.com/nef10/common-swift-package
swift swift-package-manager
Last synced: 12 days ago
JSON representation
Repo which holds and syncs files which are shared between my swift packages
- Host: GitHub
- URL: https://github.com/nef10/common-swift-package
- Owner: Nef10
- License: mit
- Created: 2021-09-04T20:42:48.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-07-08T01:50:58.000Z (4 months ago)
- Last Synced: 2024-10-10T13:28:50.020Z (29 days ago)
- Topics: swift, swift-package-manager
- Homepage:
- Size: 126 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# common-swift-package
This repository holds files which are shared between my swift packages. They are automatically synced using [this](https://github.com/BetaHuhn/repo-file-sync-action) GitHub Action:
[![Sync Files](https://github.com/Nef10/common-swift-package/actions/workflows/sync.yml/badge.svg)](https://github.com/Nef10/common-swift-package/actions/workflows/sync.yml)
## Contents
* GitHub Actions:
* CI with minimum code coverage check
* Code Coverage comment on PRs
* Documentation build with jazzy and push to GitHub pages on tag
* [Label Syncer](https://github.com/micnncim/action-label-syncer) to syncronize GitHub issue and PR labels
* [Release Drafter](https://github.com/release-drafter/release-drafter) to automatically draft release notes based on merged PRs
* [swift-dependency-updater](https://github.com/Nef10/swift-dependency-updater) running as a cron job
* Dependabot configuration to update GitHub actions
* `.swiftlint.yml` with my [default config](https://github.com/Nef10/swiftlint-config)
* `.gitignore`
* `LICENSE`## Configuration
To allow these files to serve all packages there are some configuration options:
* Place a `minimum_coverage.txt` file containing a single number in the `.github` folder to enforce a minimum code coverage percentage in the CI workflow
* Place an empty `macos_only` file in the `.github` folder to disable testing the package on ubuntu, for example when using mac only frameworks
* Place a `macos_version.txt` file containing a valid [GitHub Actions Virtual Environments label](https://github.com/actions/virtual-environments/tree/main) in the `.github` folder to run the macOS tests on a version other than `macOS-latest`