argoproj / argoproj/notifications-engine

github custom names recipient not working.

Open
#270 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
334
Forks
217
PR merge metrics
No merged PRs in 30d

Description

The docs do not include how this should work. The reason for needing custom names is we have multiple GH orgs.

```
subscriptions:
- recipients:
- slack:argocd_actions
triggers:
- on-deployed
- on-health-degraded
- on-sync-failed
- on-sync-running
- on-sync-status-unknown
- on-sync-succeeded
- recipients:
- github.ghdevops
selector: platform=true
triggers:
- on-deployed
- on-sync-failed
- on-sync-running
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the GitHub recipient configuration represented in the issue and check how the custom name `github.ghdevops` is resolved. Reproduce the shown subscription with multiple GitHub organizations, then confirm that notifications are delivered and the supported configuration is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, go
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.