@louisemcmahon something like this can work okay: Have two git remotes: origin and fork git remote rm origin git remote add origin https://github.com/nodebb/nodebb.git git remote add fork https://example.com/your/repo.git Then you can used these named remotes for updating / pushing like so: # pull and merge latest changes from NodeBB git pull origin # push latest changes to your repo git push fork That will make updating things easier.

@louisemcmahon , You can try the filters unreplied for getting all topics which don't have any reply till. https://community.nodebb.org/recent?filter=unreplied

@lewismcmahon There's no way to know what the full url is besides what's presented in config.json, since multiple URLs can point to the same NodeBB. The nconf solution is the easiest.

中文 测试discord bot

Ah that makes sense thanks

The package manager will poll npm for new changes every 10 minutes To answer your question -- yes, the compatibility table is cached, as we don't want to be pulling data from npm in real-time (that would be a tremendous waste of resources and bandwidth for npm!)