Draft
Conversation
Currently, the command-help page renders multiline command examples (the only example I've seen is for /release-note-edit) on one line, which is confusing for users. Change the style to respect newline in the source. Link: https://developer.mozilla.org/en-US/docs/Web/CSS/white-space
Seems this is a bit inconsistent with tide.
Signed-off-by: Jakub Guzik <[email protected]>
Config to automatically Re-trigger failed periodics
…6-norrs/spyglass/allow-configuration-of-sandbox-permissions-per-lense Revert "(spyglass/lenses) allow configuration sandbox permissions"
Required also `go get golang.org/x/sync` to fix compilation errors
…-20250209 deps: bump golang.org/x/*
Handle Flow Style Mapping syntax for YAML explicitly so that no silent failures are seen. Add a type check. Add a test case when invalid yaml is provided.
Signed-off-by: Jakub Guzik <[email protected]>
Change behaviour of RunAll strategy in horologium
…ishad-handle-empty-alias-group Handle empty alias group case
Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Lukas Hoehl <[email protected]>
Signed-off-by: Nikolaos Moraitis <[email protected]>
feat: introduce functional options for git v2 client factory
dump node info in the podinfo.json file
Problem: Can not set label backport-risk-assessed: Must be member in one of these teams: [] Solution: fixed the RestrictedLabelsFor() function in pkg/plugins/config.go to merge restricted label configurations across global (*) -> org -> repo levels instead of overwriting them, which was causing global teams to be lost when repository configs specified only users. Signed-off-by: Jakub Guzik <[email protected]>
Fix to properly merge lists when label is configured at global level
…terepos cherrypicker: work with private repos
This commit addresses a security vulnerability where GitHub tokens were being exposed in logs when executing git commands. The issue occurred in two places: 1. In executor.go, command arguments containing credentials were being logged without censoring sensitive information 2. In publisher.go, remote URLs with embedded tokens were being logged directly This fix ensures that sensitive information like GitHub tokens is not exposed in logs, improving the security posture of the application.
…erge (#17) - Modified the logic to check RegexpChangeMatcher conditions even when forced=true - This enables jobs with RunBeforeMerge=true to also respect run_if_changed/skip_if_only_changed conditions - Added comprehensive test cases to verify the new cooperative behavior - Preserved all existing functionality including defaults fallback behavior - All existing tests continue to pass, demonstrating no regression Co-authored-by: wuhuizuo <[email protected]> --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: wuhuizuo <[email protected]>
Signed-off-by: liubog2008 <[email protected]>
feat(config): support sidecar container
…logging fix: prevent GitHub token leakage in git command logs
Move a `regexp.MustCompile` from a often-called method to package-level so that is compiled just once.
…x-compilation fix: extract regex compilation to be done just once
Signed-off-by: Purelind <[email protected]>
- Bump golang.org/x/net to v0.41.0 - Update golang.org/x/sync to v0.15.0 - Upgrade golang.org/x/text to v0.26.0 - Change github.com/dlclark/regexp2 to v1.11.0 - Adjust golang.org/x/crypto to v0.39.0 - Update golang.org/x/mod to v0.25.0 - Upgrade golang.org/x/sys to v0.33.0 - Update golang.org/x/term to v0.32.0 - Upgrade golang.org/x/tools to v0.34.0 - Add new dependencies and update checksums in go.sum
- Adjusted the cherry-pick body creation to ensure release notes are included when prowAssignments is enabled. - Updated the logic to consistently use release notes from the parent PR in both cases of cherry-pick body generation.
- Removed unnecessary comments and whitespace in `jobs_test.go` and `jobs.go` for better readability. - Updated `prow-config-documented.yaml` and `plugin-config-documented.yaml` to streamline branch protection options and added a new `reviewer_count` field in the lgtm section. - Adjusted the modification time in `bindata.go` for the spyglass lens HTML asset.
* Initial plan * Fix Jenkins operator to skip status update when build number is 0 Co-authored-by: wuhuizuo <[email protected]> --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: wuhuizuo <[email protected]>
Remove test status check and related test cases
Switch from code.getmdl.io to cdnjs for Material Design Lite assets Co-authored-by: wuhuizuo <[email protected]>
Handle fast-failing Jenkins jobs by setting appropriate state and description based on build result (success, failure, aborted, or unknown). Set pending time and mark job as complete. Added corresponding test cases for each state.
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
20 participants
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.
No description provided.