<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">If you have commit access to MacPorts and the pull request author <a href="https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork" class="">allows it</a>, you can rebase their fork's branch (for example, with git commit --amend --no-edit) and trigger a new CI build. I’d ask before doing this though, since it’ll kill their Git history.<div class=""><br class=""></div><div class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Saagar Jha</div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On May 19, 2019, at 14:21, Rainer Müller <<a href="mailto:raimue@macports.org" class="">raimue@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 19.05.19 20:45, Christopher Chavez wrote:<br class=""><blockquote type="cite" class="">On 5/19/2019 1:40 PM, Mark Anderson wrote:<br class=""><blockquote type="cite" class="">making it possible to re-run CI from GitHub commits.<br class=""></blockquote><br class="">As a PR submitter, one workaround I'm aware of is rebasing the PR<br class="">commit(s). I'm not sure that's something members can/should try though,<br class="">so a better solution is probably still preferred…<br class=""></blockquote><br class="">I would not consider this a workaround, but the best choice we have.<br class=""><br class="">Re-running the build with the exact same revision would not be that<br class="">useful. Without changes to the source, I would expect the same result.<br class="">As the ports tree and therefore the dependencies have usually advanced<br class="">since the PR was submitted, it makes sense to do a rebase first before<br class="">attempting another build.<br class=""><br class="">In theory it is possible to restart a build on the Travis CI web<br class="">interface with the same revision, but I am not even sure if all members<br class="">have access to that?<br class=""><br class="">Rainer<br class=""></div></div></blockquote></div><br class=""></div></body></html>