Repository navigation
chore: merge main back into develop (no file changes) - #266
Merged
Merged
Conversation
ci: add the release workflow to main so it can be dispatched against develop commits
ci: add the release workflow's Mac capacity script to main
# Conflicts: # .github/scripts/release-mac-capacity-test.py # .github/scripts/release-mac-capacity.py
3 of 7 tasks
This file contains hidden or 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.
Part of #89 (audit 6 Oct: develop was 5 commits behind main).
#255 and #256 added the release workflow and its Mac capacity scripts to
mainso the release could be dispatched; develop already had the same files. This merge records main's history in develop. The tree is identical to develop e844fb5 (add/add conflicts resolved to develop's copies), so main and develop stop diverging.Candidate: bb698a6 (tree = e844fb5^{tree}). The pre-push gate passed.