Make api-fix check the apis of all tracked files, not just those with changes.

"jiri api fix" was only regenerating the .api fils for files that
differed from those in master.  This led to some strange behavior:

* A file had to be committed before "jiri api fix" would generate the
  .api file for it.

* If a file changed and .api file was generated, but then the original
  file was reverted to be the same as on master, then "jiri api fix"
  would never update the .api file back to what it was.

This CL makes "jiri api fix" generate .api files for all tracked files
in the project, not just those that differ from master.

As a side-effect, it found some files in the jiri repo that expose a
public api that did not have a corresponding .api file.

MultiPart: 2/2
Change-Id: I3f2e41cbd32d292083dd3a409c8073860f858cea
1 file changed
tree: 1827ba59cf5fae1fb0d1da9208682e5144c04ecb
  1. bendroid/
  2. dashboard/
  3. data/
  4. godepcop/
  5. gologcop/
  6. internal/
  7. jiri-api/
  8. jiri-contributors/
  9. jiri-copyright/
  10. jiri-dockergo/
  11. jiri-go/
  12. jiri-goext/
  13. jiri-oncall/
  14. jiri-profile-v23/
  15. jiri-run/
  16. jiri-swift/
  17. jiri-test/
  18. jiridoc/
  19. mailer/
  20. oncall/
  21. postsubmit/
  22. presubmit/
  23. tooldata/
  24. tracify/
  25. vbinary/
  26. vcloud/
  27. vjenkins/
  28. vkiosk/
  29. vmon/
  30. .gitignore
  31. .godepcop
  32. .jiriignore
  33. AUTHORS
  34. CONTRIBUTING.md
  35. CONTRIBUTORS
  36. LICENSE
  37. PATENTS
  38. README.md
  39. VERSION
README.md

This repository contains developer tools used to install and contribute to Vanadium.

For more information, see the installation and contributing instructions.

This repository is fetched and the tools are built as part of the Vanadium installation process for contributors.