You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I cloned repo and uninstall and reinstalled MGit app, but app keep shows specific repository.
I tried remove repo from app by UI, It successfully delete repo in Android/data/com.manichord.mgit/files/repo/{reponame},
BUT after again uninstall and reinstall, It keep shows repo and remains repo files..!
I removed manually Android/data/com.manichord.mgit/files/repo/{reponame} directory with file manager app, app settings,
but it's keep remains repo files.... or re-generate?
It happens specific repo not all repos.
I can't understand.... why
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
removing repo
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Device: Galaxy S20
OS: Android 13
App Version 1.6.2
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I cloned repo and uninstall and reinstalled MGit app, but app keep shows specific repository.
I tried remove repo from app by UI, It successfully delete repo in
Android/data/com.manichord.mgit/files/repo/{reponame}
,BUT after again uninstall and reinstall, It keep shows repo and remains repo files..!
I removed manually
Android/data/com.manichord.mgit/files/repo/{reponame}
directory with file manager app, app settings,but it's keep remains repo files.... or re-generate?
It happens specific repo not all repos.
I can't understand.... why
To Reproduce
Steps to reproduce the behavior:
Expected behavior
removing repo
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: