Skip to content

Conversation

@sparksis
Copy link

@sparksis sparksis commented Nov 4, 2024


For more details, open the Copilot Workspace session.

…ADME

* Add a new entry for the GitHub Actions workflow_call notification service in the "Productivity Based Notifications" section
* Provide an example syntax for the new notification service
@sparksis
Copy link
Author

sparksis commented Nov 4, 2024

@maintainers, apologies if this creates noise. I'll delete the PR if the tests fail locally by the end of the day 🙇

@sparksis
Copy link
Author

Will revisit the future.

@sparksis sparksis closed this Nov 29, 2024
@caronc
Copy link
Owner

caronc commented Nov 29, 2024

No need to close this, I'm sorry, i just hadn't had a chance to look further at it

@caronc caronc reopened this Nov 29, 2024
@caronc
Copy link
Owner

caronc commented Dec 7, 2024

Does this work for you if you do it manually; i don't see where this is documented very well. I found this gist which does a similar action but uses different headers and payloads.

@caronc
Copy link
Owner

caronc commented Dec 7, 2024

Also, triggering a workflow doesn't really fit with the error/info/warning/success status states Apprise passes along with each call. Would these be simply ignored for this? I still see a use case for this... the schema is way to long though. Change it to somehting like githubwf:// or maybe just github:// ?

The url may need to be something like:

  • schema://token@repository/workflow (as you have) ... but also:
  • schema://token@repository/workflow1/workflow2/workflow3 ... support multiple workflows?

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.

2 participants