disable buildomat #251
Merged
disable buildomat #251
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since #236, quartz has utilized self-hosted GitHub Actions for CI. The reasons for which are documented in a buildomat feature request. Up until this PR, the buildomat jobs still ran in parallel to the GHA jobs but were not merge-blocking and may still be running awhile an auto-merge had been enabled. Given buildomat is vestigial at this time we are opting to disable it while leaving the configuration in place for the ease of switching back in the future should our FPGA-team needs be better supported by it.