-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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
Auto-generate CMake file lists in GitHub action #10592
Auto-generate CMake file lists in GitHub action #10592
Conversation
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.
This is awesome! Can we test this before submitting it though? The only way to tell if this is actually working (AFAICT) is to submit this PR, and then submit a dependency change that shuffle the cmake file list
e5b8b49
to
1daa296
Compare
I did test it out on my personal fork and confirmed that it worked there, but I guess the only way to know for sure that it works in the main repo is to submit it and see what happens. That's a good idea to shuffle the file list, I think I'll try that afterward as a way to confirm that the action works. |
Nice, that's more than anything I thought of! As long as the functionality works any breakages will likely just be from config/settings |
8a69fef
to
24e166e
Compare
This GitHub action will run after each pull request merge and will auto-update the file lists in in src/file_lists.cmake. The action will run as our bot account. I realized that if a bug somehow made the file generation non-idempotent, this could trigger an infinite loop of commits, so I put in an extra safeguard against that. If the previous commit was by "Protobuf Team Bot", the GitHub action will revert any local changes to ensure that no new commit will be made.
24e166e
to
1f203ec
Compare
This GitHub action will run after each pull request merge and will auto-update the file lists in in src/file_lists.cmake. The action will run as our bot account.
I realized that if a bug somehow made the file generation non-idempotent, this could trigger an infinite loop of commits, so I put in an extra safeguard against that. If the previous commit was by "Protobuf Team Bot", the GitHub action will revert any local changes to ensure that no new commit will be made.