Repository navigation
chore: introduce development integration workflow - #38
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Summary
Enable normal CI and release-configuration checks for development integration pushes and PRs. Document feature PRs targeting development, version bumps during release preparation, and merge-commit promotion from development to master. The signed release workflow and version/build-number strategy are unchanged.
Testing
Actionlint for all client workflows, 12 fast release/signing checks, and git diff --check passed. Flutter application code is unchanged; no Flutter suite was rerun.
UI evidence
Not applicable.
Compatibility and migration
Development was created from the current master and is now the default branch. Existing versions, signing settings, deployment endpoints, and release history are unchanged.
Notes
Merge this PR into development. The pending mobile auth/Goals fixes remain separate. Release promotions must use Create a merge commit; bring master back into development afterwards.
Checklist