Allow for a cron workflow to trigger notification

Open
#3,092 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
bash, macos, python
Domain
cli, desktop

Research direction

No source file, test, or entry point is named. Start by locating the workflow and notification entry points, then clarify the cron configuration, command execution, stdout-based notification behavior, and macOS scope; done means a scheduled bash or Python command can run and display its output as a native notification.

Written by the indexing model from the issue text.

Description

area:warp-drive enhancement triaged
Discord username (optional)

No response

Describe the solution you'd like?
I would like to have a simple interface that allows for a cron schedule to trigger a notification. 

I want to be able to write bash or python that periodically wakes up, checks the state of something, sends a native macOS notification, and shuts down.  

- Something important in AzureDevOps
- Spark job completes
- Specific New Relic Error Type
Is your feature request related to a problem? Please describe.
* I've tried to create something similar but managing so many scripts becomes difficult.
* No easy way to use native macOS notifications with ad-hoc cron jobs. 

Workflows + the already built-in macOS notifications seem like they would be a great fit. 

name: test-py
cron: some-cron-schedule
command:  poetry run python test.py
notification: uses the std out from the command
Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.