New blog post does not show up in fleek build preview if commit was amended

[meandavejustice]

It appears that blog posts are not built properly in ci if the commit was amended. This is currently happening with https://github.com/ipfs/ipfs-blog/pull/510 and happened previously with https://github.com/ipfs/ipfs-blog/pull/509, to solve last time I opened a fresh duplicate pr, https://github.com/ipfs/ipfs-blog/pull/520. I don't want to keep cluttering up the pr queue with these duplicate prs 😬.

This may be an upstream issue with Fleek's workflow actions https://github.com/FleekHQ/workflows, but logging here until I get more info

[vesahc]

Hi @meandavejustice, sorry I missed this. This has been an ongoing issue with many Fleek sites and I've been in contact with them to resolve it. We're making progress, but we still might see a few stuck PR's occasionally.

As you've figured out the best way is to create a new PR. There is another workaround that can unblock stuck builds in cases where we need to keep comments, approvals, etc. This does seem to only unblock the build previews for a handful of commits, sometimes requiring more updates to the "cloned" branch/PR to unblock them again.

I found a workaround! You need to create a new PR for the same commit using different branch name. This will kick the build upon completion both original and new PR will get status update. Then you can merge the original and close the new one.

If PR was created from remote repository you can pull the ref to your repository locally by following these instructions:

https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch origin pull/{id}/head:temporary

git push origin temporary

source: https://stackoverflow.com/questions/52200096/github-pull-request-waiting-for-status-to-be-reported

[vesahc]

According to Fleek support this should be resolved for all future PRs. Existing PRs may still be stuck and will still need to be "forced". I'm trying to keep an eye out for those, but if anyone gets blocked please ping me here or on Slack.