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
In one browser, create a new ADR and "commit and push".
In the other browser, you will not see the new ADR.
Note that you cannot refresh the browser page to update the list of ADRs.
Workaround
You can disconnect and reconnecting will force everything to be reloaded.
If you add a second branch, you can switch between the branches to force a refresh for just that repository. Any changes will be lost.
Thoughts
For each repository in the addedRepositories list, the git commit SHA1 should be stored next to the branch.
A small background task can periodically check for new content (e.g., on browser focus if last check was 30+ seconds ago).
To make conflict resolution easier, each ADR may want to keep a git commit SHA1 for the editedMd showing what commit the edits are relative to. That way, you could try to re-apply the diff to the new originalMd.
An alternative is to use the git blob SHA1 since that is all you really care about.
The text was updated successfully, but these errors were encountered:
How to reproduce:
Workaround
branch
, you can switch between the branches to force a refresh for just that repository. Any changes will be lost.Thoughts
For each repository in the
addedRepositories
list, the git commit SHA1 should be stored next to thebranch
.A small background task can periodically check for new content (e.g., on browser focus if last check was 30+ seconds ago).
To make conflict resolution easier, each ADR may want to keep a git commit SHA1 for the
editedMd
showing what commit the edits are relative to. That way, you could try to re-apply the diff to the neworiginalMd
.An alternative is to use the git blob SHA1 since that is all you really care about.
The text was updated successfully, but these errors were encountered: