Repository navigation
Conversation
…repos Part of a series that detects which telemetry providers, such as Datadog or Google Cloud, a project uses, from its events and its repo's dependencies and config. Seer then suggests connecting a provider only when the project uses it, not when its name happens to show up in the run's evidence. Seer needs to know where a project's code is inside its repo, so that in a monorepo it reads that project's dependencies and not another service's. It also needs to know how the repo was linked, since a repo matched only by name is a weaker link than one a user chose. This sends both with each repo in the project preferences Seer reads.
github-actions
Bot
added
the
Scope: Backend
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of a series that detects which telemetry providers, such as Datadog
or Google Cloud, a project uses, from its events and its repo's
dependencies and config. Seer then suggests connecting a provider only
when the project uses it, not when its name happens to show up in the
run's evidence.
Seer needs to know where a project's code is inside its repo, so that in
a monorepo it reads that project's dependencies and not another
service's. It also needs to know how the repo was linked, since a repo
matched only by name is a weaker link than one a user chose. This sends
both with each repo in the project preferences Seer reads.