In your repo’s settings, at the bottom, you can
Transfer to a new organisation, namely YunoHost-Apps. The CI runs are automated once your app is listed in
YunoHost/apps/apps.json. Though you may need to wait a week? Not sure
Ah, ok. Is the workflow to send pull requests and somebody must merge them?
I can transfer it now and then fork it, to work on it and create pull requests?
If you transfer it now I can then take 2 seconds to give you back full right access, no need to PR from your own fork. Bear in mind, the best practice is to develop in the
testing branch and PR into
master. But if your app is still being worked on, that will be tolerated I guess.
I get this error:
Oops, I had to invite you to join the organisation first.
How can i activate https://dash.yunohost.org/appci/app/pyinventory ?
It should be automated, along with the CI.
So i have just to wait? Before it generally start or is there no CI run on every commit?
I concede it is not crystal clear about that point, but you can have a read into the documentation and the other pages too.
The automated CI are triggered only when you merge into the default branch specified in
apps.json. But there can be is a long queue.
If you want to have intermediary tests for debugging, then you can use a VM with
package_check or use the dev CI mentioned in the page Iinked.
Ah! That’s it. It was wrong configured by me. Current branch was main but i switched to master
I correct this in https://github.com/YunoHost/apps/pull/1035 (Pull is merged now)
As I said, it is all automated. ARM test is already scheduled, while
unstable tests seem to be offline. Not your fault.
You can click on the
x days ago link to go to the CI runner websites and see their status. The ARM tests are quite slow, since they are run on a couple of RPi, I think.
The whole CI is so slow. It’s not really a continues thing
Hope it’s soon possible to get a faster pipeline, but for this topic we have already a thread here: Package-check usage in a virtual machine?!?