Skip to content

Conversation

@jmriego
Copy link

@jmriego jmriego commented Jan 1, 2026

Description

I have created a script and sync side for Tasks in Markdown format. Specially following the format used in Obsidian.
It includes the title of the tasks, the completion status and the due/scheduled and done dates.

https://publish.obsidian.md/tasks/Introduction

Fixes # (issue) #121

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to
    not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

I have ran many manual tests including trying to break the syncronization. The main issue is that Markdown tasks are just text so there's no way of having a stable id. The way I have tried to solve that is to pickle changes in hash ids from tasks titles coming from Google Tasks. It saves a hidden file in the same directory as the tasks Markdown itself.

  • Test basic synchronization
  • Test empty files
  • Test changes in task title coming from Google Tasks
  • Changes in tasks titles in Markdown
  • Check for changes simultateously in both sides (for conflicts)

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Any dependent changes have been merged and published in downstream modules

@jmriego
Copy link
Author

jmriego commented Jan 1, 2026

This is ready to go but it would be missing some unit tests. Before I do that I'd like to check that in general you're ok with the approach and anything you'd like me to change or improve on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant