Merged
Conversation
…and extract changelog content up to "Additional Context". Update `DeployedActionUseCase` to close issues and log the action. Modify `DeployAddedUseCase` to utilize new changelog extraction utility. Add tests for changelog extraction functionality.
…deployment and improve changelog extraction utility. Update `DeployedActionUseCase` to close issues and log actions, while modifying `DeployAddedUseCase` to utilize the new changelog extraction method. Update type definitions accordingly.
…sure to after merges to default and development branches, enhancing logging and result reporting. Update steps to reflect new closure timing and improve clarity in deployment outcomes.
|
To view this pull requests documentation preview, visit the following URL: docs.page/landamessenger/git-board-flow~288 Documentation is deployed and generated using docs.page. |
elisalopez
changed the title
1 task
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…tBranch to be set when currentConfiguration is undefined, improving branch management during renaming operations.
…o README and features documentation, enhance issue and pull request templates, and clarify AI model configurations. Adjust concurrency settings in various workflows to support sequential execution, improving overall workflow management.
…requirements and environment variable handling. Enhance documentation on provider credentials and usage in GitHub Actions workflows.
…ronment variables for provider credentials in GitHub Actions, detail alternatives for using `/connect` in CI, and provide examples for local provider configurations. Improve overall guidance for setting up OpenCode with various providers.
…ners to use `ubuntu-latest`, add new input parameters for priority labels and AI reasoning, and improve comment handling in the ThinkUseCase to allow responses without user mention for help or question issues. Update documentation to reflect these changes.
… `branches-ignore`, enhance permissions for file updates, and streamline build and test steps. Remove obsolete validation workflow for agent processes.
…lows to streamline configuration in `gbf_issue_comment.yml` and `gbf_issue.yml`. Also, remove `opencode-start-server` parameter from `release_workflow.yml` for improved clarity.
…escriptions and hotfix changelogs, clarify steps for issue and PR management, and enhance troubleshooting guidance for action skips. Adjust workflow execution parameters for hotfixes in GitHub Actions.
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…lify component usage for a consistent UI. Revise configuration documentation to improve clarity on OpenCode integration and troubleshooting steps. Add new content sections in features and index pages for better navigation and user guidance.
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…tion configurations, including AI-generated PR descriptions. Remove outdated pull request and single actions documentation to streamline content and improve navigation.
…ent `listIssueComments`, `listPullRequestReviewComments`, `createReviewWithComments`, and `updatePullRequestReviewComment` in their respective repositories. Introduce `getPullRequestHeadSha` method for retrieving the head commit SHA of a pull request. Update constants to include a hidden HTML comment prefix for bugbot findings.
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…` with `detect-potential-problems` in CLI and documentation. Update related constants and remove obsolete `detect-errors` use case. Enhance README and documentation to reflect changes in command functionality and usage.
…penCodeRetry` function for handling retries on OpenCode HTTP requests. Update `opencodePrompt` and `opencodeMessageWithAgent` functions to utilize this retry mechanism. Remove obsolete `detect-errors` command and related references in the CLI and documentation. Enhance tests to cover retry behavior and update constants for retry configurations.
…tialProblemsUseCase` to prevent creating PR review comments when no valid file/line is found, ensuring only issue comments are added. Modify `resolveFindingPathForPr` to return undefined for invalid paths, enhancing path validation. Update tests to reflect these changes and improve clarity in comment creation behavior.
… Implement logic to preserve key configuration values from previous states when current values are undefined. Update the `update` method in ConfigurationHandler to ensure proper merging of configurations. Modify path resolution logic in CheckChangesIssueSizeUseCase to utilize development branches when parentBranch is not defined, improving robustness in branch handling. Update tests to reflect these changes and ensure expected behavior.
elisalopez
added
the
size: XXL
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…: Simplify step messages by removing size and progress details, ensuring clarity in the output of label synchronization tests.
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…eclaration of the payload variable in the update method from let to const for improved clarity and to enforce immutability, ensuring that the payload remains unchanged throughout its scope.
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
…IssueToPrUseCase: Remove detailed step messages related to size and progress labels, simplifying the output and ensuring consistency in the results. Update tests to reflect these changes and verify that steps are now empty.
efraespada
force-pushed
the
bugfix/287-release-deploy-issues
branch
from
c9f48e0 to
78774b5
Compare
elisalopez
reviewed
Feb 10, 2026
…e number, title length, and changelog size in both hotfix and release workflows to ensure proper input formats and constraints before proceeding with updates.
…lues in the files object to maintain consistency and improve clarity in type definitions.
efraespada
force-pushed
the
bugfix/287-release-deploy-issues
branch
from
94f219a to
daa64c1
Compare
Contributor
🐛 Bugfix Actions
🚀 Happy coding! |
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
2 participants
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
This PR fixes issues in the deployment system where:
deployedlabel was applied after successful deploymentThe changelog extraction now properly captures content from the "Changelog" (or "Hotfix Solution") section up to the "Additional Context" section. Additionally, when the
deployedlabel is applied after a successful deployment, the issue is now properly closed after merging to the default and development branches.🎯 Related Issues / Tickets
🧩 Scope of Changes
Added:
extractChangelogUpToAdditionalContextutility function for parsing changelog content from issue bodiesDeployedActionUseCaseafter successful mergesUpdated:
DeployedActionUseCaseto close issues whendeployedlabel is applied and all merges succeedDeployAddedUseCaseto move issues to "In Progress" whendeploylabel is addedRefactored:
🛠️ Technical Details
The changelog extraction uses a regex pattern that handles both
##and###heading styles, capturing all content from the specified section (Changelog/Hotfix Solution) up to the "Additional Context" section. This ensures the release body contains only the relevant changelog content without the additional context section.For issue closure, the
DeployedActionUseCasenow performs the following sequence:deploylabel exists anddeployedlabel is not already setdeploywithdeployedThis ensures issues are only closed when the deployment is fully complete and code has been properly merged to both branches.
🔍 How to Test
deploylabel to trigger deploymentdeployedlabel is applied🧪 Test Coverage
🚀 Deployment Notes
🔒 Security Considerations
📈 Performance Impact
📝 Notes for Reviewers
Pay special attention to the merge sequence logic in
DeployedActionUseCase- the issue should only be closed when both merges succeed. For hotfixes, the merge strategy merges the hotfix to default first, then merges default to develop (to ensure develop gets the hotfix changes).✅ Checklist
📚 Additional Context
The issue closure logic only triggers when there is an active release or hotfix branch configured. If no branch is configured, the labels are still updated but the issue remains open since no merge operations are performed.