Commits
- Commit:
1f9436b4527e40695ba3334a40f72ee9a4b16e6d- From:
- ale <ale_bnes@tuta.com>
- Date:
Add .got-backup/ to .gitignore
- Commit:
f5a98fd61e6d865c16600739c063daaa4b9dca6d- From:
- ale <ale_bnes@tuta.com>
- Date:
Actualizar README, descripción del plugin y changeNotes para 0.2.1
Documenta el soporte de clone agregado (README, plugin.xml) y sube la
versión a 0.2.1.
- Commit:
5fbd71374af6fcbdf415765ab7001f4a7a6d7322- From:
- ale <ale_bnes@tuta.com>
- Date:
Resolver GOT_AUTHOR automáticamente desde git config si el repo no lo define
got.conf de un repo recién clonado solo trae el remote, no un author, así
que got commit fallaba con "GOT_AUTHOR environment variable is not set"
en cualquier repo clonado sin configuración manual previa. Ahora se
resuelve user.name/user.email vía git config como fallback -- got.conf y
la config local del repo siguen ganando por precedencia, así que esto
nunca pisa un author explícito. Confirmado en vivo contra un repo real.
- Commit:
d0d47588e6e7212652f98d758170e30ee404ed6d- From:
- ale <ale_bnes@tuta.com>
- Date:
Agregar soporte para clonar repos got por SSH desde el diálogo nativo de IntelliJ
Registra "Got" en el dropdown "Version control" del diálogo Clone
Repository (CheckoutProvider) con un panel propio de URL/Directory --no
hereda de DvcsCloneDialogComponent porque esa clase de Git4Idea es
@ApiStatus.Internal y rompe verifyPlugin. El clone corre en dos pasos
(got clone crea el repo bare, got checkout puebla el work tree) a través
de CloneableProjectsService, el mismo mecanismo que usa Git4Idea para que
el proyecto clonado termine en Recent Projects. La URL solo acepta
ssh://, que es el único protocolo que este plugin soporta para clonar.
- Commit:
9ad5985df1ea8ce7f124e05009ea579d466d1142- From:
- ale <ale_bnes@tuta.com>
- Date:
Ignorar NOTES.md (notas de contexto solo para uso local)
- Commit:
ee44f00ccbdcf7ef792a7e364fe1d1986b343c8f- From:
- ale <ale_bnes@tuta.com>
- Date:
Limpiar comentarios narrativos y actualizar README/plugin.xml para 0.2.0
Recorta comentarios que narraban el proceso de investigacion (referencias
a decompilar clases, bugs anteriores ya resueltos, etc.) dejando solo el
'por que' no obvio de cada decision. Actualiza el README, cambeLog y la
descripcion del plugin.xml para reflejar las funciones agregadas en esta
version: pestana Log, boton Commit and Send, deteccion real de commits
salientes, got como VCS distribuido, y refresco automatico del panel de
Commit y el Log tras commit/push/update o cambios externos.
- Commit:
d21e4af15cb6b519e3dfcb3b542be7d68939fcf9- From:
- ale <ale_bnes@tuta.com>
- Date:
Add GotVcsRootWatcher to handle external VCS state changes
- Commit:
17c566b35d4b85e92568459cf8ad7cd2859a7188- From:
- ale <ale_bnes@tuta.com>
- Date:
agregar un whatcher
- Commit:
04c2af68751f50eaed7904c47754829b53eb1c1c- From:
- ale <ale_bnes@tuta.com>
- Date:
Remove default parameter in GotVcsLogProvider to fix reflective instantiation issue
- Commit:
c20235ebf75e6aca44381b87eab66aa3efee8961- From:
- ale <ale_bnes@tuta.com>
- Date:
Add `GotVcsRefreshNotifier` to streamline VCS root updates for Commit and Log panels.
- Commit:
72c6ec218af4da0b1abb8c7740c3e1fd3e9e1eef- From:
- ale <ale_bnes@tuta.com>
- Date:
Simplify `GotCommitAndSendExecutor` by delegating commit handling to `CommitContext` and removing redundant logic
- Commit:
f4f674a37c137f1977cd8043a8a05de6752f9277- From:
- ale <ale_bnes@tuta.com>
- Date:
Add push dialog invocation after commit if `PUSH_AFTER_COMMIT_KEY` is set
- Commit:
a3f6382b95b1085b8c2ba724827d033669b9b5b8- From:
- ale <ale_bnes@tuta.com>
- Date:
Refactor `doCommit` to delegate explicit path list commits via `commitFilePaths`.
- Commit:
f3ca72ddd01412bbbba872218e1fdf805b1cf72d- From:
- ale <ale_bnes@tuta.com>
- Date:
test: verificar si got commit funciona tras got add
- Commit:
8128d7171e1abbe938af4d31a39eda58a14b2b02- From:
- ale <ale_bnes@tuta.com>
- Date:
Improve VCS compatibility: refactor content handling, optimize push operations, and implement distributed commit features.
- Commit:
0136c7f3483e8e3c7bd5dcc9f78978b00e7e192b- From:
- ale <ale_bnes@tuta.com>
- Date:
Update file chooser to use `singleFile()` with title and description
- Commit:
32987097d1ec6fcc39f2f3c9e01b0fe27056d3ff- From:
- ale <ale_bnes@tuta.com>
- Date:
Add caching for commit objects and implement helper functions for commit IDs, changed paths, and refs
- Commit:
8dbfee5e7ee5620aa0d91fb7010f25f6b75f286f- From:
- ale <ale_bnes@tuta.com>
- Date:
Set `jvmDefault` to `NO_COMPATIBILITY` in Kotlin compiler options to align with plugin verifier requirements.
- Commit:
4843328d3c1fb02343e9fefc280ab6889f568093- From:
- ale <ale_bnes@tuta.com>
- Date:
Corregir GotPushSupport.getDefaultTarget: sobrecarga de 2 argumentos
PushSupport declara dos getDefaultTarget: la de un argumento es abstracta,
pero la de (repositorio, fuente) tiene cuerpo por defecto que siempre
retorna null (verificado con javap). El dialogo de Push llama a esa
segunda version, y al recibir null marca el modelo con un error de
'empty target' y loadCommits corta la ejecucion antes de invocar
GotOutgoingCommitsProvider -- por eso nunca aparecia el log de diagnostico
agregado antes y el boton de Push quedaba deshabilitado pese a existir
commits reales. Se agrega la sobrecarga faltante delegando a la de un
argumento. Mismo patron de bug que CheckinEnvironment.commit() (fase de
commit/rollback), donde la plataforma tambien encadena una sobrecarga con
valor por defecto distinta a la que se sobreescribio.
- Commit:
ff770dc4d5be7e3ede81e0fccd9df5987c526a13- From:
- ale <ale_bnes@tuta.com>
- Date:
Anadir diagnostico al proveedor de commits salientes y popup del widget de rama
GotOutgoingCommitsProvider ahora registra en el log de IntelliJ el remote,
la rama, el hash remoto resuelto y los ids encontrados en cada llamada, y
ya no deja escapar excepciones que no sean VcsException (antes se perdian
en silencio dentro del ExecutorService del dialogo de Push sin quedar
registradas en idea.log). Esto es para diagnosticar por que el boton de
Push sigue sin habilitarse pese a existir commits pendientes reales.
Tambien se implementa GotBranchWidget.getWidgetPopup(), que antes no
existia (el valor por defecto de la plataforma es null, por lo que no
pasaba nada al hacer click en el widget). Ahora muestra un popup no
interactivo con el log reciente cacheado en GotRepository (mismo patron
que branch/revision, calculado fuera del EDT).
- Commit:
f980e76321979183bd8dd6cc67f93d08fced21db- From:
- ale <ale_bnes@tuta.com>
- Date:
Implementar deteccion real de commits pendientes de enviar
Anade remoteBranchHash/outgoingCommitIds/catCommit a GotCommandLineWrapper
(basados en got ref -l, got log -x y got cat <hash>), y una clase
GotFullCommitDetails que adapta un GotCommitObject a VcsFullCommitDetails.
GotOutgoingCommitsProvider ahora resuelve el hash de la rama remota y lista
los commits no alcanzados por ella en vez de devolver siempre una lista
vacia, lo que permite que el dialogo de Push nativo detecte y habilite el
boton de envio con commits reales pendientes.
- Commit:
1723d2ac5388915746d7cd9c84279116898690a1- From:
- ale <ale_bnes@tuta.com>
- Date:
Fix EDT violation in GotRepository.getCurrentBranchName()
Reported in vivo: the branch widget never showed anything, and opening
the Push dialog hit 'Synchronous execution on EDT' (got info run
directly from PushController.createTreeModel on the UI thread) --
the same category of bug fixed earlier for GotContentRevision.
getCurrentBranchName()/getCurrentRevision() now return cached fields
instead of shelling out to got info on every call. State is read once
eagerly on construction and refreshed in update(), which the platform
calls off the EDT during a repository refresh cycle.
- Commit:
7ec62b12361bdec10782a2cd24c4125cf0585d98- From:
- ale <ale_bnes@tuta.com>
- Date:
Replace the simple Send action with a native Push dialog
Adds GotPushSource/GotPushTarget/GotPusher/GotOutgoingCommitsProvider/
GotPushTargetPanel/GotPushSupport, wired to the Repository model added
previously. This enables IntelliJ's native Push dialog (Ctrl+Shift+K)
for got send, showing the current branch and target ('origin/<branch>')
the same way Git does, instead of a plain menu action with no preview.
GotOutgoingCommitsProvider reports an empty outgoing-commits list: got
has no cheap local way to compute what a send would push without
contacting the server first, so the dialog works but doesn't preview
commits ahead of time. GotPushTargetPanel is read-only (got resolves
its own remote/branch via got.conf), unlike Git's editable target.
GotSendAction is removed; the same got send functionality is now
reached through the Push dialog instead of a VCS Operations Popup
entry.
- Commit:
7479a8a7b30eb85db1b28e9dd920a4f13791a563- From:
- ale <ale_bnes@tuta.com>
- Date:
Add a Repository model and a branch-name status bar widget
GotRepository/GotVcsRepositoryCreator/GotRepositoryManager plug into
the platform's shared DVCS infrastructure (VcsRepositoryManager,
AbstractRepositoryManager) rather than reimplementing repository
tracking from scratch. GotBranchWidget (built on DvcsStatusWidget,
the same base class git4idea's own branch widget uses) shows the
current branch next to the project name in the main toolbar, matching
Git's UI.
Requires new compile dependencies on intellij.platform.vcs.dvcs and
intellij.platform.vcs.dvcs.impl: Repository/RepositoryManager and the
status widget base classes live outside com.intellij.modules.vcs.
This Repository model is also the prerequisite for real PushSupport
(native Ctrl+Shift+K dialog), which follows next.
- Commit:
4a9d1c555f6ed4615c6b891e5d20aa1c6b4644a0- From:
- ale <ale_bnes@tuta.com>
- Date:
Add status badges to the README
GitHub Actions release workflow status, latest GitHub release version,
GPLv3 license, and JetBrains Marketplace version/downloads (plugin
33099).
