TT-15793 added workflow to Suggest target branches#7511
Conversation
🎯 Recommended Merge TargetsBased on JIRA ticket TT-15793: Implement Intelligent Branch Merge Recommendations Fix Version: Tyk 5.10.1Required:
📋 Workflow
|
|
API Changes no api changes detected |
🔍 Code Analysis ResultsThis PR introduces a new GitHub Actions workflow to automatically suggest target branches for pull requests based on information from an associated Jira ticket. Files Changed Analysis
Architecture & Impact Assessment
graph TD
A[Pull Request Event] --> B{Trigger 'PR Merge Suggestions' Workflow};
B --> C{Execute 'branch-suggestions' Job};
C --> D[Call Reusable Workflow<br>TykTechnologies/github-actions/branch-suggestion.yml];
D -- Uses JIRA_TOKEN --> E[Fetch Info from Jira];
E --> F[Calculate Branch Suggestions];
F --> G[Post Suggestions as a PR Comment];
Scope Discovery & Context Expansion
Metadata
Powered by Visor from Probelabs Last updated: 2025-11-06T11:13:15.653Z | Triggered by: synchronize | Commit: b9880f1 💡 TIP: You can chat with Visor using |
🔍 Code Analysis ResultsSecurity Issues (1)
Architecture Issues (1)
Performance Issues (1)
Quality Issues (1)
✅ Dependency Check PassedNo dependency issues found – changes LGTM. ✅ Connectivity Check PassedNo connectivity issues found – changes LGTM. Powered by Visor from Probelabs Last updated: 2025-11-06T11:13:16.949Z | Triggered by: synchronize | Commit: b9880f1 💡 TIP: You can chat with Visor using |
|
<!-- Provide a general summary of your changes in the Title above --> ## Description <!-- Describe your changes in detail --> ## Related Issue <!-- This project only accepts pull requests related to open issues. --> <!-- If suggesting a new feature or change, please discuss it in an issue first. --> <!-- If fixing a bug, there should be an issue describing it with steps to reproduce. --> <!-- OSS: Please link to the issue here. Tyk: please create/link the JIRA ticket. --> ## Motivation and Context <!-- Why is this change required? What problem does it solve? --> ## How This Has Been Tested <!-- Please describe in detail how you tested your changes --> <!-- Include details of your testing environment, and the tests --> <!-- you ran to see how your change affects other areas of the code, etc. --> <!-- This information is helpful for reviewers and QA. --> ## Screenshots (if appropriate) ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Refactoring or add test (improvements in base code or adds test coverage to functionality) ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply --> <!-- If there are no documentation updates required, mark the item as checked. --> <!-- Raise up any additional concerns not covered by the checklist. --> - [ ] I ensured that the documentation is up to date - [ ] I explained why this PR updates go.mod in detail with reasoning why it's required - [ ] I would like a code coverage CI quality gate exception and have explained why <!---TykTechnologies/jira-linter starts here--> ### Ticket Details <details> <summary> <a href="https://tyktech.atlassian.net/browse/TT-15793" title="TT-15793" target="_blank">TT-15793</a> </summary> | | | |---------|----| | Status | In Dev | | Summary | Implement Intelligent Branch Merge Recommendations | Generated at: 2025-11-05 14:15:34 </details> <!---TykTechnologies/jira-linter ends here--> Co-authored-by: sredny buitrago <sredny@srednys-MacBook-Pro.local>



Description
Related Issue
Motivation and Context
How This Has Been Tested
Screenshots (if appropriate)
Types of changes
Checklist
Ticket Details
TT-15793
Generated at: 2025-11-06 11:09:32