Is MR required for a non-suggested version?

I’m working on a separate branch for my published app, and I would like to tag some intermediate steps so that those temporary versions will be available, but I don’t want to let F-Droid show them as “suggested”.
Currently F-Droid is automagically retrieving and publishing everything I’m tagging on master branch.

So, do I need a MR to do that, or there is another way?



We don’t have “unstable/alpha/beta” entries in the metadata, this is being worked on for index-v2.

So yes, manual MRs that point to commit hashes is the workflow.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.