Agate
Agate
No worries, we're all pretty busy. Feel free to tell me if there is anything I can do to speed up / help with the reviewing process.
Hey @mineo, thank you for your hard work on this, I'm really happy to hear things are moving forward !
Hi @dskrad, thank you for opening the issue. Until this is properly documented, you can find below a custom blueprint I have that includes visualizations: ```json { "id": "agate:travel", "label":...
I've give it some thoughts and I think it should be done outside of the project: I have no experience with GraphQL and won't be able to test and maintain...
If you feel like implementing and maintaining it, it's a different story then. I can't provide much guidance on the GraphQL aspects, but I'm up to review or help with...
Regarding the merge conflict issue, maybe [this kind of setup](https://docs.weblate.org/en/latest/admin/continuous.html#avoiding-merge-conflicts) could offer a solution ?
thank you for your work on this @papey, I'm going to try it soon on https://blog.funkwhale.audio!
Possibly linked to https://github.com/Plume-org/Plume/issues/450, and closable when Generic Timelines are implemented :)
thank you @KitaitiMakoto, I'm not using Plume anymore, but I still think it's an improvement!
Closing because of inactivity, and we have migrated to github actions since then