Azure DevOps doesn't have an official API to retrieve user permissions for a project or a repository. As a stopgap solution, I've defaulted all issue and comment authors to RepoAssociationMember. This is probably a good minimum bar.
The audit log is the best way to retrieve the repository creation date, but this may not be enabled. So I am using the first repository commit as a fallback value.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)
implement `ListIssues` and `GetCreatedAt` for Azure DevOps
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
ListIssues
andGetCreatedAt
throw an unsupported errorWhat is the new behavior (if this is a feature change)?**
ListIssues
andGetCreatedAt
have implementationsWhich issue(s) this PR fixes
Next step of https://github.com/ossf/scorecard/issues/4177
Special notes for your reviewer
Azure DevOps doesn't have an official API to retrieve user permissions for a project or a repository. As a stopgap solution, I've defaulted all issue and comment authors to
RepoAssociationMember
. This is probably a good minimum bar.The audit log is the best way to retrieve the repository creation date, but this may not be enabled. So I am using the first repository commit as a fallback value.
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to the
release-note
(In particular, describe what changes users might need to make in their application as a result of this pull request.)