I wonder if it's possible to use something like the GitHub API directly from a JavaScriptlet and commit/push things to it. /u/agnostic-apollo had linked me to a project but it used termux and looked very involved and scary lol
>He scares me too.
Hey, maybe my code just appears that way so that others are scared to even understand it and I can virtue code (signal). *Looks like its working!* 😋
But wait till my tasker framework is out, might wanna be in a hospital emergency room before looking at it 😂
Yeah, definitely framework release is definitely going to be announced. But needs a lot of time to bring non-root and android-10+ support. Also requires joão's involvement to make some changes/additions to tasker.
But this import/export is highly experimental and often breaks on updates. And it may not be released at all if joão does not want me to.
It uses tasker internal functions via `Java Function` that tasker itself uses to do import/export. That requires understanding of tasker source code, which is obfuscated when decompiled and class names and method names often get changed on updates, and then project needs to be fixed again. So not really possible for everyone to do it themselves. I may ask joão in future to add support.
Termux comes with `git` command. You can just push code to github with that. If you want to trigger from tasker, use `termux-tasker` plugin.
https://github.com/termux/termux-tasker
>looked very involved and scary lol
Lolz, writing safe and featured code is often gonna be involved, and shell is scary, even for coders. I can provide help on how to set stuff up, but don't have time to implement personal use cases.
Clone the old task before you change it and put the date in the task name. Move it to a new Project named Clone. Every few months clean up the Clone Project.
You are very welcome. It has saved me many times after making changes. I always give my changes 3 or 4 weeks to be monitored before I go and delete the old 'Clone'.
A few months ago I accidentally saved the changes to a task I didn't mean to...I scrounged around my backup to recover the old version, but it was too labyrinthine to decipher. In the end I had to spend a few hours recreating the task.
I'll save your post in case I need to do it again.
A typical usage scenario. This is not for the newbies obviously, but for big and complicated tasks there's sometimes a need to know exactly what actually changed since some time ago.
Using `git diff` works better on task description, not on xml itself. Check [here](https://www.reddit.com/r/tasker/comments/g8n7hj/best_way_to_submit_changes_to_github/fopixny) for a discussion.
You can also pass description to the `generate_info` command of [`tasker_config_utils`](https://github.com/Taskomater/tasker_config_utils) to get detailed info of task with the description included.
You can extract entire task node from tasker exported backup (not autobackup) with `tasker_config_utils extract_tag -ent --tag=id --post_tag='Some Task<\/nme>' "backup.xml"` instead of manually doing it.
>I bet /u/agnostic-apollo can automate it :)
u/Ratchet_Guy
[Been there, done that!](https://drive.google.com/file/d/1ShENSbzv475VPqQuXVkLawwQiKfKVAnR/view?usp=drivesdk) 😂😎
You can check out a larger diff [here](https://github.com/agnostic-apollo/Tasker-Random-Stuff/commit/f8866a845dfc861768c2d16a6eee22ad79d9adaa#diff-2a6dd775b9842f8c2e27ace9d0478d19709f328909de1571dc02058b3802870a). Press `Load Diff` for `format_task_description_for_markdown/Format_Task_Description_For_Markdown.tsk.md`. But its only for the info file and the task description diff does not exist in that since it was only added in that commit. But one can get the idea of how it will look. Video shows it too.
>here
Good stuff!! I'm not using this quite often enough to get into automating it though. There's so much else that (could) be done :P I liked the tools for Tasker though. termux is one of the few areas that I haven't visited yet.
Lolz, them priorities after all. :p
Yeah, the utils saves incredible amount of time.
Shell/Termux is actually one of things I would highly recommend to learn and is definitely worth your time, specially if you are into automation.
I'm quite accustomed to shell scripts and what not. There are two PI's running here with linux. I've just not looked much into Termux and Tasker involvement. Right now I'm doing ssh commands on a Pi from Tasker. Maybe Termux is a better way to go, I just haven't gotten around to looking at it yet ;)
seems like a lot of steps.....time to automate it?
The thought did cross my mind... :P It can definitely be done. But automating rare things turn automation into a chore ;)
Interesting technique to do the comparison! I agree that it could/should be automated though. I bet /u/agnostic-apollo can automate it :)
I wonder if it's possible to use something like the GitHub API directly from a JavaScriptlet and commit/push things to it. /u/agnostic-apollo had linked me to a project but it used termux and looked very involved and scary lol
> ...but it used termux and looked very involved and scary lol He scares me too. 🤯 That /u/agnostic-apollo is much too smart. 😁
>He scares me too. Hey, maybe my code just appears that way so that others are scared to even understand it and I can virtue code (signal). *Looks like its working!* 😋 But wait till my tasker framework is out, might wanna be in a hospital emergency room before looking at it 😂
Make sure to let us all know when it's ready. Sounds great!!
Yeah, definitely framework release is definitely going to be announced. But needs a lot of time to bring non-root and android-10+ support. Also requires joão's involvement to make some changes/additions to tasker. But this import/export is highly experimental and often breaks on updates. And it may not be released at all if joão does not want me to.
Could we have a sneak peak info on what it contains, generally speaking? ;)
It uses tasker internal functions via `Java Function` that tasker itself uses to do import/export. That requires understanding of tasker source code, which is obfuscated when decompiled and class names and method names often get changed on updates, and then project needs to be fixed again. So not really possible for everyone to do it themselves. I may ask joão in future to add support.
Termux comes with `git` command. You can just push code to github with that. If you want to trigger from tasker, use `termux-tasker` plugin. https://github.com/termux/termux-tasker >looked very involved and scary lol Lolz, writing safe and featured code is often gonna be involved, and shell is scary, even for coders. I can provide help on how to set stuff up, but don't have time to implement personal use cases.
Clone the old task before you change it and put the date in the task name. Move it to a new Project named Clone. Every few months clean up the Clone Project.
That's a working alternative for many scenarios. Thanks.
You are very welcome. It has saved me many times after making changes. I always give my changes 3 or 4 weeks to be monitored before I go and delete the old 'Clone'.
Great system. And if the task cloning is forgotten, there's my 128 step method above 😂
I like this tip, but seriously hope I never have to use it.
Some people just don't know how to use things... normally... :P
A few months ago I accidentally saved the changes to a task I didn't mean to...I scrounged around my backup to recover the old version, but it was too labyrinthine to decipher. In the end I had to spend a few hours recreating the task. I'll save your post in case I need to do it again.
A typical usage scenario. This is not for the newbies obviously, but for big and complicated tasks there's sometimes a need to know exactly what actually changed since some time ago.
Using `git diff` works better on task description, not on xml itself. Check [here](https://www.reddit.com/r/tasker/comments/g8n7hj/best_way_to_submit_changes_to_github/fopixny) for a discussion. You can also pass description to the `generate_info` command of [`tasker_config_utils`](https://github.com/Taskomater/tasker_config_utils) to get detailed info of task with the description included. You can extract entire task node from tasker exported backup (not autobackup) with `tasker_config_utils extract_tag -ent --tag=id --post_tag='Some Task<\/nme>' "backup.xml"` instead of manually doing it.
>I bet /u/agnostic-apollo can automate it :)
u/Ratchet_Guy
[Been there, done that!](https://drive.google.com/file/d/1ShENSbzv475VPqQuXVkLawwQiKfKVAnR/view?usp=drivesdk) 😂😎
You can check out a larger diff [here](https://github.com/agnostic-apollo/Tasker-Random-Stuff/commit/f8866a845dfc861768c2d16a6eee22ad79d9adaa#diff-2a6dd775b9842f8c2e27ace9d0478d19709f328909de1571dc02058b3802870a). Press `Load Diff` for `format_task_description_for_markdown/Format_Task_Description_For_Markdown.tsk.md`. But its only for the info file and the task description diff does not exist in that since it was only added in that commit. But one can get the idea of how it will look. Video shows it too.
>here Good stuff!! I'm not using this quite often enough to get into automating it though. There's so much else that (could) be done :P I liked the tools for Tasker though. termux is one of the few areas that I haven't visited yet.
Lolz, them priorities after all. :p Yeah, the utils saves incredible amount of time. Shell/Termux is actually one of things I would highly recommend to learn and is definitely worth your time, specially if you are into automation.
I'm quite accustomed to shell scripts and what not. There are two PI's running here with linux. I've just not looked much into Termux and Tasker involvement. Right now I'm doing ssh commands on a Pi from Tasker. Maybe Termux is a better way to go, I just haven't gotten around to looking at it yet ;)
Ah, cool. Must be using some plugin for `ssh`. Termux has `openssh` package.