mirror of
https://github.com/pd4d10/git-touch.git
synced 2026-03-21 21:51:42 -05:00
Continuous release #196
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/git-touch#196
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @iTrooz on GitHub (Nov 4, 2022).
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 ?
@DinuruSeniya commented on GitHub (Nov 17, 2022):
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.
ERR : Because git_touch depends on antd_mobile from path which doesn't exist (could not find package antd_mobile at "../ant-design-mobile-flutter"), version solving failed.It'd be helpful to have an updated app built on new versions of Flutter.
In the meantime, I'd suggest forking and working on it, so you don't need to wait for dev approval.
@iTrooz commented on GitHub (Nov 17, 2022):
The problem is that
Even if you meant just preparing the PR in advance, my last point still apply
@zen0bit commented on GitHub (Dec 17, 2023):
I am interested...
@Nevarro commented on GitHub (Jan 10, 2024):
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.
@AkechiShiro commented on GitHub (Jan 13, 2024):
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
@Nevarro commented on GitHub (Jan 24, 2024):
@pd4d10 Is there any chance for further development?
@michaelblyons commented on GitHub (Jan 20, 2025):
Some time ago, I asked F-Droid about the possibility of continuing from a fork. They said they'd need permission from the original owner or a new app name and icon.
Several forks seem to have carried the torch forward. (@Catzoy most recently?) If one of them is interested in publication, the above might be of note.