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
Within one minute after saving a change to a Markdown file in _pages in GitHub, an error email from GitHub comes:
Clicking through to GitHub, see this:
Some 6 minutes later, (in the past, within a minute) get another email:
This has occured multiple times, whenever I changed any Markdown file via GitHub.
To Reproduce
Steps to reproduce the behavior:
Change index.md or about.md directly within the GitHub site via a browser (Firefox).
Check live site using Maxime Vaillancourt's template after a minute: Changes were published successfully.
Get an email from GitHub notifications saying "[kolanuts/digital-garden] Run failed: Roam Research backup - main (f1558ec)"
Expected behavior
I'd expect there to be no failure message, and for the backup to succeed.
Traceback
Run roam-to-git --debug notes/ and report what you get.
It should open a Chrome front-end, an do the scrapping. The repository content will not be modified. If applicable, add screenshots to help explain your problem.
OS: Win10
Do you use Github Action? Yes
Do you use multiple Roam databases? Yes, but only 1 is connected with my repo of course
Does roam-to-git use to work for you? (This should be "Did roam-to-git work for you previously?") I think this has happened every time, but the updates are still pushed live!
Does some backup runs are still working? (This should be "Are some backup runs still working?") I think... not? Not sure how to see this. But screenshot under Traceback suggests backups are not working.
The text was updated successfully, but these errors were encountered:
Describe the bug
Within one minute after saving a change to a Markdown file in _pages in GitHub, an error email from GitHub comes:
Clicking through to GitHub, see this:
Some 6 minutes later, (in the past, within a minute) get another email:
This has occured multiple times, whenever I changed any Markdown file via GitHub.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I'd expect there to be no failure message, and for the backup to succeed.
Traceback
Run
roam-to-git --debug notes/
and report what you get.It should open a Chrome front-end, an do the scrapping. The repository content will not be modified. If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: