We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request for Git Updater: Add the ability to view and pull specific pull requests (PRs) on a branch to enable testing of PR code.
This feature would improve testing workflows by allowing users to test PR code directly within Git Updater, without needing to switch to other tools.
Suggested functionalities include:
PR List: Display a list of available PRs for the selected branch within the Git Updater interface.
Pull Specific PR: Enable users to select and pull a specific PR for testing purposes.
Revert PR Changes: Optionally, include a quick “revert” feature to roll back the PR changes after testing.
The text was updated successfully, but these errors were encountered:
I’m not really sure how to accomplish this. Usually what I do is pull down the remote branch that has the PR and run that locally.
If the PRs are in separate branches it’s easy to switch between branches using that feature of Git Updater.
Sorry, something went wrong.
No branches or pull requests
Feature Request for Git Updater:
Add the ability to view and pull specific pull requests (PRs) on a branch to enable testing of PR code.
This feature would improve testing workflows by allowing users to test PR code directly within Git Updater, without needing to switch to other tools.
Suggested functionalities include:
PR List: Display a list of available PRs for the selected branch within the Git Updater interface.
Pull Specific PR: Enable users to select and pull a specific PR for testing purposes.
Revert PR Changes: Optionally, include a quick “revert” feature to roll back the PR changes after testing.
The text was updated successfully, but these errors were encountered: