Note that # ever圓0 will miss February, as it just checks if the day number is correct. Monthly repeats: You can use # every15 and it'll make a repeating task on the 15th of every month. So if something's part of your monday-friday routine, tag it # weekdays. The "stick an 's' on the end to make a task repeat" trick works here too. Is it Friday and you want to tag a work task for tomorrow, but not have it show up until Monday? Use # weekday. You can stick an 's' on the end of days-of-the-week to make a task repeating as well! So # mondays is equivalent to # monday # repeat. However, you probably won't need to use the # repeat tag very often, because there's usually a shorthand way to represent it. This would then just show up as &) review my daily reminders in workflowy wf (and clicking the little WorkFlowy icon would take you to that list) Productivity in the wrong direction isn’t worth anything at all.&) review my daily reminders in workflowy # today # repeat This could be good if the task exists within workflowy: The difference is that by linking it you get a little button to click through to the node. Use # repeat instead and it'll link it but still won't tell WorkFlowy to complete the task. if you complete it it won't tell WorkFlowy) Those should now also work with Complice, though they might change that format any time which could break it.Īdd # nolink to the WorkFlowy node, and it will pull it in but not link the Complice intention with the node (so eg. WorkFlowy is beta-testing built-in dates, including ranges. That task will only get pulled in on that day if you miss it, Complice will forget about it. You can also tag a task with a specific date in YYYY-MM-DD format. If you don't do it that day, it'll get pulled again the following week. If you tag something with a day of the week, it will get pulled on that day. your list is empty (this fetch is automatically triggered after you complete your outcomes). If you tag something # tomorrow, it will get pulled only when you're first setting your intentions, i.e. If you tag something # today, it will get pulled whenever you press fetch. Also note that the arrows, calendars, and other symbols that show up in the tags below are not something you have to manually enter-they're displayed by a custom style (see the bottom of this page). Usually it's due to a typo in the format, not a software bug. If it seems to not be working, re-read this guide before contacting support. (The reverse doesn't happen same-day, but if you complete a node in WorkFlowy then it won't be pulled into Complice on future days.) When you set your intentions, the tasks are linked to workflowy, and checking off the task in Complice means it'll be marked done in WorkFlowy too. The "pull from workflowy" action will get automatically triggered after you complete your outcomes, to pull in intentions for the next day. ![]() You can fetch them using a button next to your intentions box that looks like this: The basic idea is to put Complice intentions in WorkFlowy, and then tag them with the date that you want them to show up in your intentions drafts. It's a great place to break down goals into projects and projects into tasks, and that's why it pairs so nicely with Complice, which intentionally deprioritizes organizing, and focuses on a fresh list every day. Pipelines for schedules or merge requests don’t run either, because no rules evaluate to true for them.WorkFlowy is an epic infinite-tree organizer, that lets you create bullet lists of bullet lists of bullet lists, and zoom in to any level of the tree.Pipelines for push events with -draft in the commit message don’t run, because.Pipelines run for all push events (changes to branches and new tags).See the common if clauses for rules for more examples. if: $CI_COMMIT_BRANCH Control when branch pipelines run. ![]() if: $CI_COMMIT_TAG Control when tag pipelines run. if: '$CI_PIPELINE_SOURCE = "push"' Control when both branch pipelines and tag pipelines run. Some example if clauses for workflow: rules: Example rules Details if: '$CI_PIPELINE_SOURCE = "merge_request_event"' Control when merge request pipelines run. For example, if a job is configured to runįor tags, but the workflow prevents tag pipelines, the job never runs. The workflow keyword is evaluated before jobs. Use the workflow keyword to control when pipelines are created.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |