You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many of the discourse documentation topics are marked as wiki topics which enables community edits. These edits could be pulled back as PRs to make proposed changes. One implementation could be to look at the edit reason field and set the to a special value if done through automation and only consider the edits not done through the automation. Would also need to consider what to do with any chages that are about to be overidden by a run of the action
The text was updated successfully, but these errors were encountered:
The logic can be pull down and changes since the last change by the automation (indicated either by the last edit reason including the unique key for the automation or as being done by the same user the automation is running as since the action currently does not have a edit reason that is highly likely to be just used by the automation) are pulled down and included as a single PR on the repository. This would be run before the updates are run so as not to lose those changes. The action would also have a mode where it just does this so that it can be run periodically if desired
Many of the discourse documentation topics are marked as wiki topics which enables community edits. These edits could be pulled back as PRs to make proposed changes. One implementation could be to look at the edit reason field and set the to a special value if done through automation and only consider the edits not done through the automation. Would also need to consider what to do with any chages that are about to be overidden by a run of the action
The text was updated successfully, but these errors were encountered: