That worked! Thank you.

@nebulon Awesome, thank you so much!

Interesting... I do the opposite. I star on GitHub and i am happy that i don't need to go into release bell to turn on notifications.

I guess we can add a default though.

I have fixed this now and made a new app package for it. It was just a client-side display issue, so you projects should already show the name without having to re-add it.

@nebulon thank you, the API calls are dramatically reduced.

Updated now

@nebulon I added a new toke and it seems to work, thanks!

@nebulon this is a recent example of the app log:

Sep 20 17:57:13 releasebell/tasks run: start +1h Sep 20 17:57:13 releasebell/tasks syncGithubStarredByUser: ABCDEFG +1ms Sep 20 17:57:13 releasebell/tasks syncGithubStarredByUser: found 8 starred repos +360ms Sep 20 17:57:13 releasebell/tasks syncGithubStarredByUser: new projects: 0 outdated projects: 0 +14ms Sep 20 17:57:13 releasebell/tasks syncReleasesByProject: [cloudron/box] type gitlab start sync releases. Last successful sync was at 2020-09-20T14:56:58.470Z +18ms Sep 20 17:57:15 releasebell/tasks syncReleasesByProject: [cloudron/box] found 0 new releases +1s Sep 20 17:57:15 releasebell/tasks syncReleasesByProject: [cloudron/box] successfully synced +0ms Sep 20 17:57:15 releasebell/tasks syncReleasesByProject: [cloudron/ghost-app] type gitlab start sync releases. Last successful sync was at 2020-09-20T14:56:59.407Z +11ms Sep 20 17:57:16 releasebell/tasks syncReleasesByProject: [cloudron/ghost-app] found 0 new releases +997ms Sep 20 17:57:16 releasebell/tasks syncReleasesByProject: [cloudron/ghost-app] successfully synced +0ms Sep 20 17:57:16 releasebell/tasks syncReleasesByProject: [cloudron/matomo-app] type gitlab start sync releases. Last successful sync was at 2020-09-20T14:57:00.470Z +2ms Sep 20 17:57:17 releasebell/tasks syncReleasesByProject: [cloudron/matomo-app] found 0 new releases +934ms Sep 20 17:57:17 releasebell/tasks syncReleasesByProject: [cloudron/matomo-app] successfully synced +1ms

Back in the day we used to use an external service to track all the products. I forgot what it's called but it shutdown. We made releasebell as a replacement for that service. That other service used to simply track starred repos. Just explaining why Releasebell is the way it is right now. It was a simple clone.

I did look into integrating with gogs when I did the GitLab integration. IIRC, the issue was that the gogs APIs for release tracking required a token (unlike GitHub and GitLab). This means that you have to create an account in another gogs/gitea instance (registration is frequently disabled) making it impossible to track. I think we might have to investigate a bit more and report the issue upstream first.

That did it! Thanks!

Hi,

I have not really thought of that use-case for it thus far, but have created an issue at the project's page https://git.cloudron.io/cloudron/releasebell/issues/2