initial fastlane structures from IzzyOnDroid#3293
initial fastlane structures from IzzyOnDroid#3293ahmedre merged 3 commits intoquran:mainfrom IzzySoft:fastlane
Conversation
|
Thanks for opening this PR - I am not using Fastlane today (using GitHub Actions) and this PR is adding resources - will these resources added in the correct folders allow IzzyOnDroid to automatically update the descriptions whenever a new deployment / new version is released? |
No contradiction. You will notice this PR does not include any Fastlane binaries, as those are not needed for the intended purpose (though you could use them of course if you wanted).
Exactly that is the purpose of this PR, and about establishing these structures in your repo here, yes! Whenever a new release is being "pulled over", we also create a fresh clone of your repo, and then sync the fastlane tree – to bring over everything you might have changed, while unchanged files stay untouched. Quoting from the initial comment above:
|
|
@ahmedre any chance to get this merged? As we need to move on with our repo reorg at IzzyOnDroid, it would help us a lot. Thanks in advance! |
|
I don't feel too keen on having a fastlane folder in the project when we don't support fastlane - but the docs say you're ok with one of either /metadata root or /src//fastlane/metadata/android// (though I guess if the latter is in the root directory it'd be more confusing). can we go with the /metadata option instead? |
|
Sure we can – I just stick to the standards, when possible. Give me a minute, I adjust that in my PR, as you suggest. |
|
Done. |
|
|
thanks, merging - heads up though I am planning to push another update to the apk hopefully this weekend as I iron out issues from the current release |
|
Thanks! Activated at our end now. Changes you apply now will be synchronized whenever a new release is being pulled in – which, as usual, should be detected automatically and pulled within 24h of your making it and attaching an APK to it. |
this PR provides you with a "fastlane starter package" – to give it into your hands to define how your app is presented, and make it easy to keep descriptions & graphics in sync with your development. Some notes to sum them up in a place easy to find for you:
full_description.txtmax 4,000 chars, graphics must have specific aspect ratios etc.full_description.txthere I've used HTML compressed into a single line, to prevent the fdroid software converting each line break to a<br>. The tags used for this are supported by F-Droid.org as well, and to my knowledge even by PlayStore.The second commit adds the missing IzzyOnDroid badge to the Readme.
And now: Enjoy!