Skip to content

Update/ci#2854

Open
yubiuser wants to merge 6 commits intospecial/CI_developmentfrom
update/CI
Open

Update/ci#2854
yubiuser wants to merge 6 commits intospecial/CI_developmentfrom
update/CI

Conversation

@yubiuser
Copy link
Copy Markdown
Member

This is #2853 after resolving the merge conflicts.

DL6ER and others added 6 commits December 13, 2025 11:40
Signed-off-by: Dominik <dl6er@dl6er.de>
Signed-off-by: Dominik <dl6er@dl6er.de>
Signed-off-by: Dominik <dl6er@dl6er.de>
Signed-off-by: Dominik <dl6er@dl6er.de>
…uarantees clearing of the whole union (except for static storage duration initialization), it just initializes the first union member to zero.

Signed-off-by: Dominik <dl6er@dl6er.de>
Signed-off-by: yubiuser <github@yubiuser.dev>
@yubiuser yubiuser requested a review from a team as a code owner April 18, 2026 18:24
@yubiuser yubiuser mentioned this pull request Apr 18, 2026
1 task
@yubiuser
Copy link
Copy Markdown
Member Author

Mhhh... maybe I got confused which branch needs to be merged into which branch.

@DL6ER Is there any special handling inside special/CI_development? Or can we just replace that branch 1:1 with the current development without needing to merge/rebase?

@DL6ER
Copy link
Copy Markdown
Member

DL6ER commented Apr 20, 2026

Yes, the typical workflow is a hard reset on development and force push onto this one. It's not used for anything besides the internal tests during upgrades of the ftl-build container

@DL6ER DL6ER force-pushed the special/CI_development branch from 9365126 to d35f22d Compare April 20, 2026 17:23
@DL6ER
Copy link
Copy Markdown
Member

DL6ER commented Apr 20, 2026

What is update/CI supposed to do? I just manually reset special/CI_development to development

@yubiuser
Copy link
Copy Markdown
Member Author

It was intended to solve the merge conflict I observed in #2853 were I just tried to merge developemt straight into special/CI_development

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants