ctubbsii commented on PR #3165: URL: https://github.com/apache/accumulo/pull/3165#issuecomment-1404061200
You can still stage on your clone to run GitHub Actions in your fork... and then fix any issues by adding fixes to your local branch before pushing up. You don't need to create a PR to trigger GitHub Actions... you can just run them in your forked repo in your branch. However, the longer you have the merge forward staged, the more conflicts you'll likely see as new activity appears on the target/main branch, so I would merge relatively quickly and fix any merge bugs as a follow-up. But, you can reduce the risk by testing the merge locally or in your fork, so when you do merge the actual commit that gets added, you have already tested it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
