While using gbp import-origin on GNOME sources (used a debian/master -
pristine-tar - upstream/latest layout) I've done the mistakes a few
times to do a gbp import-origin before doing a pull/checking if the
local checkout was uptodate.

The import does work without warning and update the 3 branches which put
you in a situation where you need to know git wizary to rollback the
buggy import and start it again.

Would it possible for gbp import commands to warn/ask for confirmation
when the checkout is outdated? (or to provide an easy command to undo
the import/fix the situation when an import is done on an outdated vcs)?

Thanks,

This would be a nice feature in git-buildpackage. There are two
potential places a user might need to remember to pull from:
- newer commits in the official git repository of the package
- newer versions in the official Debian archives in case of a NMU that
was not pushed to git

Right now users need to remember to manually run these when starting
to work on a package after a break:
gbp pull --verbose
gbp import-dsc --verbose --pristine-tar apt:<package>/sid

Related
- https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmus-from-the-maintainer-s-point-of-view
- Bug#1013294 git-buildpackage: improvement to doc to import NMUs
- Bug#1060371 git-buildpackage: feature request: gbp sync
- https://salsa.debian.org/debian/debcraft/-/issues/19
- https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/439
- https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/467