Inflectra Customer Forums: Proposal: Reviewing Pull Requests should change Git as a result (Thread) Hi all, How I understand Spiras Pull Requests: 1. It is a task that after beeing reviewed doesnt change anything on Git side, 2. Somebody should go into a Git manually and proceed with merge actions directly there. Expected behaviour that after status Under Review (or some other pull request status) it should be able to proceed with the Git merge action automaticaly without necessity to leave Spira and open any other instrument. Does Spira have this feature? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/2576.aspxthreadId=2576Ilia Poliakov (ilya.polyakov@edetek.com)git pull requestsProposal: Reviewing Pull Requests should change Git as a result Hi all, How I understand Spiras Pull Requests: 1. It is a task that after beeing reviewed doesnt change anything on Git side, 2. Somebody should go into a Git manually and proceed with merge actions directly there. Expected behaviour that after status Under Review (or some other pull request status) it should be able to proceed with the Git merge action automaticaly without necessity to leave Spira and open any other instrument. Does Spira have this feature? Sun, 20 Feb 2022 10:40:54 -05002022-02-20T14:10:19-05:00/Support/Forum/spirateam/issues-questions/2576.aspxmessageId=4270David J (adam.sandman+support@inflectra.com) That is not available currently. It is on our backlog as a feature. It is a relatively complex fea That is not available currently. It is on our backlog as a feature. It is a relatively complex feature because not only do you have to merge the branches upon successful pull request, but you have to also handle and file conflicts that may exists. There are many tools (see: https://www.inflectra.com/TaraVault/Git.aspx ) that do this very well. The Spira pull requests are used to manage the workflow between developers, document the code review and ensure that the merge is done. The actual merge and resolution should be done in your Git client. Regards David Sun, 20 Feb 2022 12:01:53 -05002022-02-20T12:04:44-05:00/Support/Forum/spirateam/issues-questions/2576.aspx#reply4270messageId=4271Ilia Poliakov (ilya.polyakov@edetek.com) I guess, the easiest way for Spira is to if a Pull Request was confirmed in Spira it should replace I guess, the easiest way for Spira is to if a Pull Request was confirmed in Spira it should replace old files in Git with the new ones with the confirmation dialog about it. Not very complicated (if no other options than just replace) but rather effective. Otherwise, for example in our company, developers are saying that pull requsests are useless: it is just plus one more tool where they should do additional clicks as fter that they should switch back to Git where duplicate there decision about pull request there. Sun, 20 Feb 2022 12:55:28 -05002022-02-20T12:55:28-05:00/Support/Forum/spirateam/issues-questions/2576.aspx#reply4271messageId=4273David J (adam.sandman+support@inflectra.com) Again not possible because of the way Git works. Overwriting files would be incorrect. You need to Again not possible because of the way Git works. Overwriting files would be incorrect. You need to handle merges and conflict resolutions. Sun, 20 Feb 2022 14:10:19 -05002022-02-20T14:10:19-05:00/Support/Forum/spirateam/issues-questions/2576.aspx#reply4273