This repository was archived by the owner on Jul 3, 2024. It is now read-only.
Added app store metadata to the repository (Gradle-play-publisher) #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* According to the F-Droid docs the file structure for this kind of metadata can be used to add metadata as long as the files are included in a tagged release. https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/ * While at the moment we (afaik) do not automatically publish to Google Play we already use Gradle. So the "Gradle Play Publisher" seems to be a good choice. (F-Droid just uses the file structure. So there is no necessity to for us to actually use the tool.) https://github.com/Triple-T/Gradle-play-publisher#managing-play-store-metadata * This commit includes: * contact-email * contact-website * title for de-DE and en-GB * short-description for de-DE and en-GB * full-description for de-DE and en-GB * a screenshot for de-DE and en-GB
|
For the record: The request to include this app within F-Droid can be found here -> https://gitlab.com/fdroid/rfp/issues/951 |
guserav
deleted the
description-and-screenshot-metadata-for-appstore-within-repository
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
According to the F-Droid docs the file structure for this kind of metadata can be used to add metadata as long as the files are included in a tagged release.
https://f-droid.org/en/docs/All_About_Descriptions_Graphics_and_Screenshots/
While at the moment we (afaik) do not automatically publish to Google Play we already use Gradle. So the "Gradle Play Publisher" seems to be a good choice. (F-Droid just uses the file structure. So there is no necessity to for us to actually use the tool.)
https://github.com/Triple-T/Gradle-play-publisher#managing-play-store-metadata
This commit includes:
This commit does not include:
I vote to simply add -1 (revision) to the v1.1 tag (v1.1-1) as to emulate the Debian versioning for added nerd factor and of course because nothing meaningful to the app itself changed.