Skip to content
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

Sync upstream 2025-01-20 #306

Closed

Conversation

nunnatsa
Copy link
Contributor

Release notes:

Sync upstream 2025-01-20

nirarg and others added 30 commits December 16, 2021 21:26
…-2021.12.23

Sync with upstream 2021.12.23
This PR adds a new github action to daily sync with upstream. It checks if there are new changes in upstream, and if there are, it creates a PR to sync.

The new PR is created by hard reseting to the upstream main branch, then restoring the downstream modified files.

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
This PR adds a new github action to daily sync with upstream. It checks if there are new changes in upstream, and if there are, it creates a PR to sync.

The new PR is created by hard reseting to the upstream main branch, then restoring the downstream modified files.

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
This PR adds a new github action to daily sync with upstream. It checks if there are new changes in upstream, and if there are, it creates a PR to sync.

The new PR is created by hard reseting to the upstream main branch, then restoring the downstream modified files.

Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
nunnatsa and others added 16 commits December 24, 2023 09:25
Signed-off-by: Nahshon Unna-Tsameret <[email protected]>
…m_2023-12-24-07-25

Auto sync upstream 2023-12-24 07:25 + update OWNER file
…m_2024-01-08-09-36

Auto sync upstream 2024-01-08 09:36
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nunnatsa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 20, 2025
Copy link

CLA Not Signed

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Jan 20, 2025
@nunnatsa nunnatsa closed this Jan 20, 2025
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 20, 2025
@nunnatsa nunnatsa deleted the sync_upstream_2025-01-20 branch January 20, 2025 08:35
@k8s-ci-robot k8s-ci-robot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Jan 20, 2025
@k8s-ci-robot
Copy link
Contributor

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the kubernetes-sigs org. You can then trigger verification by writing /verify-owners in a comment.

  • orenc1
    • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
    • OWNERS
  • nirarg
    • User is not a member of the org. Satisfy at least one of these conditions to make the user trusted.
    • OWNERS

@nunnatsa nunnatsa restored the sync_upstream_2025-01-20 branch January 20, 2025 08:35
@coveralls
Copy link

Pull Request Test Coverage Report for Build 12864017910

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 58.928%

Totals Coverage Status
Change from base Build 12863778945: 0.0%
Covered Lines: 1561
Relevant Lines: 2649

💛 - Coveralls

@nunnatsa nunnatsa deleted the sync_upstream_2025-01-20 branch January 21, 2025 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants