forked from ossf/scorecard
-
Notifications
You must be signed in to change notification settings - Fork 0
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
[pull] main from ossf:main #48
Open
pull
wants to merge
1,266
commits into
nanikjava:main
Choose a base branch
from
ossf:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
Since upgrading to v1.9.1 we've had performance issues in the weekly analysis, which may be related to one of the Maven features here. Signed-off-by: Spencer Schrock <[email protected]>
justaugustus
had a problem deploying
to
integration-test
December 17, 2024 03:06 — with
GitHub Actions
Failure
* ✨ implement more of the Azure DevOps client Includes: - `GetBranch` - `GetSuccessfulWorkflowRuns` - `ListCheckRunsForRef` - `ListStatuses` - `ListWebhooks` - `SearchCommits` Also, includes comments about methods which can never be implemented: - `GetOrgRepoClient` - Org repository, AKA the `<org>/.github` repository, is a GitHub-specific feature - `ListLicenses` - Azure DevOps doesn't have a license detection feature. Thankfully, the License check falls back to file-based detection. Still need to implement: - `ListReleases` - Needs a little more investigation to line up the Azure DevOps implementation with what Scorecard expects Signed-off-by: Jamie Magee <[email protected]> * PR comments Signed-off-by: Jamie Magee <[email protected]> * Rename tests to more accurately reflect what they do Signed-off-by: Jamie Magee <[email protected]> --------- Signed-off-by: Jamie Magee <[email protected]>
spencerschrock
had a problem deploying
to
integration-test
December 31, 2024 17:17 — with
GitHub Actions
Failure
* governance: Add meeting note archives from 2021 through 2024 --------- Signed-off-by: Stephen Augustus <[email protected]> Co-authored-by: Spencer Schrock <[email protected]>
justaugustus
had a problem deploying
to
integration-test
January 6, 2025 17:40 — with
GitHub Actions
Failure
Signed-off-by: Rachael Newitt <[email protected]>
justaugustus
had a problem deploying
to
integration-test
January 7, 2025 04:07 — with
GitHub Actions
Failure
We have gained two new repos: community and ironic-standalone-operator We have archived one repo: ironic-client Signed-off-by: Tuomo Tanskanen <[email protected]>
spencerschrock
had a problem deploying
to
integration-test
January 7, 2025 16:10 — with
GitHub Actions
Failure
…ash. (#4483) * Logging a warning if readGitHubTokens finds several values which clash. Signed-off-by: Simon Heidrich <[email protected]> * Using log.Printf instead of fmt.Printf. Signed-off-by: Simon Heidrich <[email protected]> * Removing obsolete t.Helper calls. Signed-off-by: Simon Heidrich <[email protected]> * Unsetting local env vars in tests. Signed-off-by: Simon Heidrich <[email protected]> * Using string.Builder to generate warning message, as the linter considered the line too long. Signed-off-by: Simon Heidrich <[email protected]> --------- Signed-off-by: Simon Heidrich <[email protected]>
spencerschrock
had a problem deploying
to
integration-test
January 9, 2025 15:48 — with
GitHub Actions
Failure
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.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )