infrastructure/k8s-cluster
1
0
Fork 2
Code Issues 29 Pull requests 10 Projects Releases Packages Wiki Activity

fix: kuma-next.sh there is no gap between old and recent #231

Closed
GhostPLACEHOLDER wants to merge 1 commit from refs/pull/261/head66a87d10090f1e622330175c8b116190ad78b82c into mainb7623d4bc2060d7314b1fa148acb2e859c9894df
pull from: refs/pull/261/head66a87d10090f1e622330175c8b116190ad78b82c
merge into: infrastructure:mainb7623d4bc2060d7314b1fa148acb2e859c9894df
Conversation 0 Commits 1 Files changed 1 +3 -2
GhostPLACEHOLDER commented 2025-05-29 20:17:50 +00:00
First-time contributor
Copy link

The following scenario is possible:

  • 1am: commit A is merged
  • 2am: commit B is created but not merged
  • 3am: v*.next is built out of commit A
  • 4am: commit B is merged (not squashed)

Now v*.next will run commit A but it will not be the
first commit created before 3am.

Fixes infrastructure/k8s-cluster#260

The following scenario is possible: - 1am: commit A is merged - 2am: commit B is created but not merged - 3am: v*.next is built out of commit A - 4am: commit B is merged (not squashed) Now v*.next will run commit A but it will not be the first commit created before 3am. Fixes infrastructure/k8s-cluster#260
GhostPLACEHOLDER added 1 commit 2025-05-29 20:17:50 +00:00
fix: kuma-next.sh there is no gap between old and recent
Some checks failed
build / lint (push) Has been cancelled
build / lint (pull_request) Has been cancelled
/ test (pull_request) Has been cancelled
66a87d1009 
The following scenario is possible:

- 1am: commit A is merged
- 2am: commit B is created but not merged
- 3am: v*.next is built out of commit A
- 4am: commit B is merged (not squashed)

Now v*.next will run commit A but it will not be the
first commit created before 3am.

Fixes infrastructure/k8s-cluster#260
root closed this pull request 2025-05-29 20:17:51 +00:00
Some checks failed
build / lint (push) Has been cancelled
build / lint (pull_request) Has been cancelled
/ test (pull_request) Has been cancelled

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug

Something is not working

  
cleanup

   
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
forgefriends

https://code.forgejo.org/infrastructure/k8s-cluster/src/branch/main/.forgejo/workflows/sync.yml

  
help wanted

Need some help

  
invalid

Something is wrong

  
label workflow

a workflow is associated with this issue and will trigger when labels are updated

  
need more info

   
question

More information is needed

  
refactor

No functional change, reorganization

  
static-site

https://code.forgejo.org/infrastructure/k8s-cluster/src/branch/main/.forgejo/workflows/sync.yml

  
sync

https://code.forgejo.org/infrastructure/k8s-cluster/src/branch/main/.forgejo/workflows/build.yml

  
wontfix

This won't be fixed

No labels
bug
cleanup
duplicate
enhancement
forgefriends
help wanted
invalid
label workflow
need more info
question
refactor
static-site
sync
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/k8s-cluster#231
No description provided.
Delete branch "refs/pull/261/head66a87d10090f1e622330175c8b116190ad78b82c"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?