Relative links pointing to file about to be updated #25
Description
Let's say you have a commit with two new doc files: A and B. A has a link to B, but A is processed first. When A's relative links are examined, there is no wiki page for B yet, so the link points to GitHub instead of Confluence (which would have happened had B been processed first).
One solution would be to realize that even if the page doesn't exist yet, the file is in the list of files to be synced. Maybe we can pause the processing of A and start with B. But of course, what if a commit adds two new files that link to each other?
It's not a major problem, as the simple solution is to run the workflow manually for A after the fact. I'm mostly posting here as something to think about, and in case anyone is in search of a fun challenge :)