Call org-back-to-heading with INVISIBLE-OK set to true

[punchagan]

The point can end up on the wrong headline, causing the export to
fail, when org-back-to-heading isn't called without INVISIBLE-OK.

[kaushalmodi]

It looks fine to me. Though, I haven't yet faced that error. Can you describe a workflow for which this fix is being made? When would you need to make top portion of a tree-to-be-exported invisible?

Also, as a nitpick, can you update the commit to say (org-back-to-heading :invisible-ok)? I just like the arg to be self-explaining (basically match the name of the actual arg with a colon prefix.. because t or :invisible-ok would work the same way :)

Can you also put an explanation of a scenario where using :invisible-ok would be necessary in the commit message itself?

From the commit message of the current PR:

The point can end up on the wrong headline,

Wouldn't that export the wrong tree then?

[punchagan]

Use the all-posts.org file in the example-site

1. cycle visibility of headings, until all the headings in the buffer are collapsed.
2. C-c e H A to export all the posts
   The export fails with an error indicating that HUGO_EXPORT_FILE_NAME is mandatory, with the point at the * Image subtree. The export was actually exporting the first child ** Image links, but org-back-to-heading leaves the point at the wrong location.

[kaushalmodi]

Makes sense. Thanks!