-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continuous release #292
Comments
I also support this. The current CI runner fails due to an outdated NodeJS version. However even after fixing that, I still get this error. In the meantime, I'd suggest forking and working on it, so you don't need to wait for dev approval. |
The problem is that
Even if you meant just preparing the PR in advance, my last point still apply |
I am interested... |
I'd be interested as well. I'm looking for a way to manage Forgejo/Gitea issues on iOS, maybe with push notifications on due dates. |
Is the project abandoned currently ? There hasn't been much activity on the main branch since 2 years ago, @pd4d10 @shreyas1599 It could be however that the project is close to working all fine and so far it doesn't need much updates, but I'm not sure, I believe dependencies should be kept up to date, continuous release could help with that. I'm not sure if @iTrooz is still interested and can work on his proposed idea |
@pd4d10 Is there any chance for further development? |
The last release is from over a year ago, but there seems to be a lot of changes (commits) since then.
If this is true, and if the release cycle must stay like this, I think it would be good to have a continuous release that is updated with the latest CI artifacts (which would also require a CI that build the app ofc)
I am willing to work on this, but I would like your approval (or from anyone that can merge a PR) first. Would you like such a feature ?
The text was updated successfully, but these errors were encountered: