3.4 Caveats
- Fetched information is stored in a database. The table schemata of
that database have not been finalized yet. Until that has happened
it will occasionally have to be discarded. That isn’t such a huge
deal because for now the database does not contain any information
that cannot simply be fetched again, see Initial Pull.
- Fetching is implemented under the assumption that the API can be
asked to list the things that have changed since we last checked.
Unfortunately the APIs are not bug-free, so this is not always the
case. Especially in closed-source software it can take years for
issues to get fixed, so I am no longer delaying the initial Forge
release because of that. If in doubt, then re-fetch an individual
pull-request to ensure it is up-to-date using the command
forge-pull-pullreq
.
- Some other, forge-specific, caveats are mentioned in Supported Forges and Hosts.