Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To understand..
https://github.com/LeastAuthority/destiny/blob/1.0.3/TERMS.md
instead of
https://github.com/LeastAuthority/destiny/blob/1.0.3-fdroid/TERMS.md
because according logic, we will split string via separator - and take only first part 1.0.3
However in github valid tag is 1.0.3-froid and it means file is available only
https://github.com/LeastAuthority/destiny/blob/1.0.3-fdroid/TERMS.md, not at https://github.com/LeastAuthority/destiny/blob/1.0.3/TERMS.md
In destiny application, when user clicks on Terms link we provide link to exact file of that version, that Terms version would correlate with app version.
Or maybe I misunderstand something..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The format of the tag is not affected by this change. It would just allow using a version name
1.0.3-fdroid
and still. be able to use the per version Terms URL.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But we are ok as long as we don't create tag
1.0.3-fdroid
in github tag for releasesThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A F-Droid release will be triggered with any tag in the format
1.0.3
. That-fdroid
just will be appended during the build itself.