The action checks for conflicts between git docs and discourse. However, taking into account the need to run the conflict detection check for every topic, potential rate limits and potentially large documentation, there could be on the order of minutes between the conflict check being run and the documentation actually being updated. This means that there is a window of time when there could be a community contribution that gets overridden.
There are some ideas to resolve this:
Mark the documentation topics as a draft before running the check so that other changes cannot be made in the meantime
Record the version of a topic that was current as of the conflict check and check that there were no changes after all the updates were made. If there were any changes, roll back the updates that were made automatically and fail the action
The action checks for conflicts between git docs and discourse. However, taking into account the need to run the conflict detection check for every topic, potential rate limits and potentially large documentation, there could be on the order of minutes between the conflict check being run and the documentation actually being updated. This means that there is a window of time when there could be a community contribution that gets overridden.
There are some ideas to resolve this: