/**
 * Tag matching for `includeTags` and `excludeTags`, with `*` wildcards
 * (issue #111).
 *
 * Selection was exact-match, so a team with `service-a`, `service-b`, … had to
 * enumerate every tag and remember to update the configuration whenever one was
 * added. Forgetting silently includes or excludes the wrong operations, which
 * is the failure mode the tag mechanism exists to prevent.
 *
 * The wildcard syntax and its escaping/anchoring rules live in
 * `wildcard-matching.ts`, shared with `PathMatcher` (proposal 43).
 */
/**
 * A compiled matcher for a list of tag patterns.
 *
 * Patterns without a `*` are kept in a Set and matched by equality, so the
 * overwhelmingly common case costs no more than it did before this feature and
 * behaves identically -- including for a tag that happens to contain regex
 * syntax.
 */
export declare class TagMatcher {
    private readonly exact;
    private readonly patterns;
    constructor(tagPatterns: ReadonlyArray<string>);
    get isEmpty(): boolean;
    matches(tag: string): boolean;
    matchesAny(tags: ReadonlyArray<string> | undefined): boolean;
}
//# sourceMappingURL=tag-matching.d.ts.map