Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LCFS - Investigate GitHub App/Bot for Workflow Notifications #2127

Open
hamed-valiollahi opened this issue Feb 27, 2025 · 0 comments
Open

LCFS - Investigate GitHub App/Bot for Workflow Notifications #2127

hamed-valiollahi opened this issue Feb 27, 2025 · 0 comments
Labels
Spike Research needed prior to development

Comments

@hamed-valiollahi
Copy link
Collaborator

hamed-valiollahi commented Feb 27, 2025

Problem
Our team needs an automated way to notify Microsoft Teams channels or email lists whenever our GitHub workflows run. This includes events like successful runs, failures, and possibly other relevant status updates (e.g., canceled runs). Manually relaying workflow info is time-consuming and prone to errors, so we want to build (or leverage) a GitHub App or bot that can subscribe to these events and dispatch notifications accordingly.

Goal

  1. Evaluate options for capturing workflow events (e.g., success/failure).
  2. Compare building a GitHub App/Bot vs. using existing marketplace solutions.

Solution Requirements

  • Event Handling: Track workflow runs (success, fail, canceled, etc.).
  • Security & Maintenance: Manage tokens securely and keep configuration simple.

Approach

  1. Research: Review GitHub App docs and potential third-party tools.
  2. Prototype: Build a minimal proof-of-concept or test an existing solution.
  3. Evaluate: Compare complexity, maintenance, and security. Document pros/cons.

Outcome

  • Success: Recommendation with a preferred approach and next steps.
  • Blockers: Document problems, discuss alternatives with the team.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Spike Research needed prior to development
Projects
None yet
Development

No branches or pull requests

1 participant