English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Tools annual

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Presents the access of premium content as premium feature

Premium Content

Global: Zendy Plus annual

Global: Zendy Free Plan

Encountering outdated documentation is not a rare occurrence for developersand users in the software engineering community. To ensure that softwaredocumentation is up-to-date, developers often have to manually check whetherthe documentation needs to be updated whenever changes are made to the sourcecode. In our previous work, we proposed an approach to automatically detectoutdated code element references in software repositories and found that morethan a quarter of the 1000 most popular projects on GitHub contained at leastone outdated reference. In this paper, we present a GitHub Actions tool thatbuilds on our previous work's approach that GitHub developers can configure toautomatically scan for outdated code element references in their GitHubproject's documentation whenever a pull request is submitted.

Wait, wasn't that code here before? Detecting Outdated Software Documentation