|Number of watchers on Github||211|
|Number of open issues||0|
|Average time to close an issue||less than a minute|
|Average time to merge a PR||about 3 hours|
|Open pull requests||0+|
|Closed pull requests||0+|
|Last commit||over 3 years ago|
|Repo Created||almost 4 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||afnetworking|
|Do you use fastlane? Leave a review!|
|View fastlane activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Note this is still a work in progress, and is not ready for production yet
Creating a new release for an Objective-C/Swift open source framework is a tedious process. This fastlane setup is an attempt to streamline that process by creating a single button to generate a new release, allowing developers to focus on great updates, without the overhead of creating new releases.
It is recommended to have a high level understanding of what fastlane is, but it is not required. You can read up more on fastlane here.
To install fastlane, simply use gem (related: Should I use sudo?):
[sudo] gem install fastlane
The goal is to create a one button release like so with almost no overhead for a developer.
fastlane prepare_framework_release version:3.0.0 env --deploy
That does the following:
When the tests have passed on CI, the
complete_framework_release lane will automatically run:
In order to get the most out of this tool, it is recommended you manage your Github repo with the following best practices. It's easy to do, and gives you a lot of automation power with fastlane. Below is how AFNetworking is being managed:
There are primary use cases for these fastlanes: testing and deployment. When used together, a full continuous integration system can be created.
Getting the testing harness configured is an easy process.
Follow the getting started guide to configure the framework for testing.
Getting up and running is a simple process:
A full deployment guide has been created to help get developers get started with automating deployment.
The lanes provided are divided into two groups: lanes meant for for testing, and lanes meant for deployment. In combination with the Github best practices above, developers can fully automate the release process.