feat(Repository): Use KnownProvenance instead of VcsInfo #15688
Annotations
1 error
You have commit messages with errors
⧗ input: feat(Provenance): Add `matches(KnownProvenance)` method
In preparation of replacing `VcsInfo` in `Repository` with `KnownProvenances`,
we add a method to match `KnownProvenances` against each other.
Signed-off-by: Jens Keim <[email protected]>
✖ body's lines must not be longer than 75 characters [body-max-line-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
⧗ input: refactor(Provenance): Allow blank `resolvedRevision` for `VcsInfo.EMPTY`
This will allow tests using `Repository` objects using `VcsInfo.EMPTY` to
continue to function, even though `RepositoryProvenance` does not usually
allow blank revisions. By restricting the exception to `VcsInfo.EMPTY` any
other bahaviour of `RepositoryProvenance` should be retained.
Some unrelated `OrtResultTest`s had to be given non-blank revisions:
Both `fail if no vcs matches` and `use the correct vcs` don't hinge on
the given blank revision, so to assure they do not fail for unrelated reasons,
we just add the default git revision "main" to these example repos.
Signed-off-by: Jens Keim <[email protected]>
✖ body's lines must not be longer than 75 characters [body-max-line-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
⧗ input: Readd `vcs` and `vcs_processed` temporarily
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
|
This job failed
Loading