The fossil status command will report the current status of your project, whether you have uncommitted edits and whether your working code is at the tip:

    $ fossil status
    repository:   /home/clif/myProject/../myProject.fossil
    local-root:   /home/clif/myProject/
    config-db:    /home/clif/.fossil
    checkout:     47c85d29075b25aa0d61f39d56f61f72ac2aae67 2016-12-20     
    17:35:49 UTC
    parent:       f3c579cd47d383980770341e9c079a87d92b17db 2016-12-20     
    17:33:38 UTC  
    tags:         trunk
    comment:      Ticket 1234abc workaround (user: clif) 
    EDITED     main.tcl

If there has been a commit made to the branch you're working on since your last checkout, the status will include a line resembling the following:

    child:         abcdef123456789...  YYYY-MM-DD HH:MM::SS UTC

This indicates that there is a commit after your code. You will have to do a fossil update to bring your working copy of the code into sync before you can commit to the head of the branch. This may require you to fix conflicts by hand.

Note that fossil can only report the data in your local repository. If commits have been made but not pushed to the server and pulled into your local repository, they won't be displayed. You should invoke fossil sync before fossil status to confirm that your repository has all the latest information.