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 a PR check for viability and formatting #1135
Conversation
8a4fb49
to
6711e56
Compare
Oh, lame. Looks like a tag gets exported as a SHA, so Fast-CDR makes this not work right. I'll convert this back to draft - we might be able to get the behavior we want from |
6711e56
to
28f2024
Compare
Signed-off-by: Scott K Logan <logans@cottsay.net>
28f2024
to
5415b0f
Compare
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.
I like it.
Very cool! Is there a way to run this against the current |
The workflow will need to be introduced into each branch that we want to protect, so we won't get any breakage on day 0. |
Works for me. I thought that workflows from the default branch would be a applied everywhere given the |
This change adds a simple-and-sweet import/export round-trip to verify that all of the repository information is viable and that the format matches whatvcstool
exports.This change adds some YAML format validation (including alphabetical ordering), as well as a validation pass using
vcstool
.Requires #1134