Skip to content

Grab update-yaml changes from main branch #188

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

Merged
merged 9 commits into from
Aug 19, 2025

Conversation

pjreiniger
Copy link
Contributor

@pjreiniger pjreiniger commented Jul 30, 2025

This runs the script that I have updated in robotpy/semiwrap#287, and is blocked on that getting released to have this run automatically in CI

Lots of the changes are minor formatting ones, like the removal of --- and leading newlines in the files. There were however also a few additions that hadn't been tracked in the yamls files, and a ton of deletions.

This grabs the update-yaml updates from the main branch, and ensures the outputs are good for the 2027 changes

@virtuald
Copy link
Member

I think we should do this first to main, merge that to 2027, and then update again? Otherwise we're going to have some obnoxious merge conflicts.

@pjreiniger
Copy link
Contributor Author

Yeah that makes sense. I did it on 2027 because I already had the hand-tweaked results

@pjreiniger
Copy link
Contributor Author

pjreiniger commented Aug 18, 2025

I imagine what you meant to do was merge main instead of 2027 to grab those changes. So I did that and force pushed. This should be the 2027 specific update-yaml changes

@pjreiniger pjreiniger changed the title Run new update-yaml script to resync yaml to headers Grab update-yaml changes from main branch Aug 18, 2025
@virtuald virtuald merged commit ac60fd3 into robotpy:2027 Aug 19, 2025
41 checks passed
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.

3 participants