-
-
Notifications
You must be signed in to change notification settings - Fork 395
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
Add target-gen reformat
and hexify some YAML properties
#2548
Conversation
Little brother, he says. PR is still |
target-gen refresh
and hexify some YAMLtarget-gen refresh
and hexify some YAML properties
I did my best to keep the comments, but it's evident we'll need to somehow automate that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are three ways I can think of to de-risk this a little:
- Identify a cross section of targets that need to be tested, and use the Matrix channel to do a call for volunteers to test this branch.
- Merge this to master, and be sure we don't release for at least 2 months. This will allow all master branch users and contributors to implicitly test this. If there are surprises, we can easily restore in master.
- Keep a compressed version of the pre-change yaml's in master for now, with a flag on probe-rs to revert these if a user wants to do comparison troubleshooting.
I'm OK with 2 or 3, if you are willing to 'recover' when the need arises.
As this is basically just a bunch of reformatting, I'm willing to bet some of my free time that merging this is safe :) We can always revert the merge commit. |
target-gen refresh
and hexify some YAML propertiestarget-gen reformat
and hexify some YAML properties
This is the little brother of #2543 without the target and flash algo deduplication.