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

Add target-gen reformat and hexify some YAML properties #2548

Merged
merged 7 commits into from
Jun 6, 2024

Conversation

bugadani
Copy link
Contributor

@bugadani bugadani commented Jun 6, 2024

This is the little brother of #2543 without the target and flash algo deduplication.

@bugadani
Copy link
Contributor Author

bugadani commented Jun 6, 2024

Little brother, he says. PR is still +76,264 −80,295 OMG. That is mostly whitespace change, though, I believe

@bugadani bugadani marked this pull request as draft June 6, 2024 11:37
@bugadani bugadani changed the title Add target-gen refresh and hexify some YAML Add target-gen refresh and hexify some YAML properties Jun 6, 2024
@bugadani
Copy link
Contributor Author

bugadani commented Jun 6, 2024

I did my best to keep the comments, but it's evident we'll need to somehow automate that.

@bugadani bugadani marked this pull request as ready for review June 6, 2024 11:56
Copy link
Contributor

@noppej noppej left a 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:

  1. 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.
  2. 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.
  3. 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.

@bugadani
Copy link
Contributor Author

bugadani commented Jun 6, 2024

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.

@bugadani bugadani added this pull request to the merge queue Jun 6, 2024
@bugadani bugadani removed this pull request from the merge queue due to a manual request Jun 6, 2024
@bugadani bugadani changed the title Add target-gen refresh and hexify some YAML properties Add target-gen reformat and hexify some YAML properties Jun 6, 2024
@bugadani bugadani enabled auto-merge June 6, 2024 12:44
@bugadani bugadani added this pull request to the merge queue Jun 6, 2024
Merged via the queue into probe-rs:master with commit ac5b417 Jun 6, 2024
19 checks passed
@bugadani bugadani deleted the refresh2 branch June 6, 2024 12:56
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