Skip to content

update: follow symlinks when scanning for fastlane

For apps with different build flavours:
This way they can e.g. have different descriptions per flavour, but use symlinks to share changelogs, instead of duplicating files.

Specific example: Gadgetbridge has two flavours: main and banglejs
We tried symlinking from the banglejs Fastlane directory to the main changelog, but that doesn't work, because it doesn't follow the link when looking for <CurrentVersionCode>.txt.

With this change it does work.

Merge request reports