Skip to content

ref(ingest): Make feed-ingest-triage the issue channel #918

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

Closed
wants to merge 1 commit into from

Conversation

loewenheim
Copy link

This changes the channel for triage notifications for the ingest team from #discuss-ingest to #feed-ingest-triage.

Copy link

codecov bot commented Jun 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.25%. Comparing base (b579361) to head (99450e2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #918   +/-   ##
=======================================
  Coverage   89.25%   89.25%           
=======================================
  Files         123      123           
  Lines        3805     3805           
  Branches      759      759           
=======================================
  Hits         3396     3396           
  Misses        395      395           
  Partials       14       14           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@@ -186,7 +186,7 @@ teams:
team-ingest:
offices:
- vie
slack_channel: C019637C760
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah I was hoping you'd git log this file and notice it is generated :)

@asottile-sentry
Copy link
Member

this file is generated this won't help

@loewenheim
Copy link
Author

@asottile-sentry Maybe I'm missing something, but #906 and #912 seem to have manually edited this file.

@asottile-sentry
Copy link
Member

and nobody from the owning team reviewed them until after merge -- where hubert pointed out they did it wrong: #906 (comment)

@loewenheim
Copy link
Author

In security-as-code: https://github.com/getsentry/security-as-code/pull/1646

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.

3 participants