Console interface to Gerrit Code Review
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

93 lines
3.3 KiB

  1. # This is an example ~/.config/gertty/gertty.yaml file for use with
  2. # installations of Gerrit running on googlesource.com. Most of these options
  3. # are not required, rather, they customize Gertty to better deal with the
  4. # particulars of Google's Gerrit configuration.
  5. # This file does not list all of the available options. For a full
  6. # list with explanations, see the 'reference-gertty.yaml' file.
  7. servers:
  8. - name: CHANGEME-review
  9. url: https://CHANGEME-review.googlesource.com/
  10. # Get username and password at https://{name}-review.googlesource.com/#/settings/http-password
  11. # It will provide a gitcookies file with contents like this:
  12. # gerrit-review.googlesource.com FALSE / TRUE 2147483647 o git-user.example.com=ooghaGhu7ohva5xai8LahcheoVahTae5
  13. # The username in this example is "git-user.example.com" and the
  14. # password is "ooghaGhu7ohva5xai8LahcheoVahTae5". They are
  15. # separated by an "=" character.
  16. # Note this is not your Google password.
  17. username: CHANGEME
  18. password: CHANGEME
  19. auth-type: basic
  20. git-root: ~/git/
  21. # Uncomment the next line if your terminal has a white background
  22. # palette: light
  23. # Commentlinks are regexes that are applied to commit and review
  24. # messages. They can be replaced with internal or external links, or
  25. # have colors applied.
  26. commentlinks:
  27. # Match Gerrit change ids, and replace them with a link to an
  28. # internal Gertty search for that change id.
  29. - match: "(?P<id>I[0-9a-fA-F]{40})"
  30. replacements:
  31. - search:
  32. text: "{id}"
  33. query: "change:{id}"
  34. # Uncomment the following line to use a unified diff view instead
  35. # of the default side-by-side:
  36. # diff-view: unified
  37. # This section defines customized dashboards. You can supply any
  38. # Gertty search string and bind them to any key. They will appear in
  39. # the global help text, and pressing the key anywhere in Gertty will
  40. # discard the current display stack and replace it with the results of
  41. # the query.
  42. #
  43. # NB: "recentlyseen:24 hours" does not just return changes seen in the
  44. # last 24 hours -- it returns changes seen within 24 hours of the most
  45. # recently seen change. So you can take the weekend off and pick up
  46. # where you were.
  47. dashboards:
  48. - name: "My changes"
  49. query: "owner:self status:open"
  50. key: "f2"
  51. - name: "Incoming reviews"
  52. query: "is:open is:reviewer"
  53. key: "f3"
  54. - name: "Starred changes"
  55. query: "is:starred"
  56. key: "f4"
  57. - name: "Recently seen changes"
  58. query: "recentlyseen:24 hours"
  59. sort-by: "last-seen"
  60. reverse: True
  61. key: "f5"
  62. # Reviewkeys are hotkeys that perform immediate reviews within the
  63. # change screen. Any pending comments or review messages will be
  64. # attached to the review; otherwise an empty review will be left. The
  65. # approvals list is exhaustive, so if you specify an empty list,
  66. # Gertty will submit a review that clears any previous approvals. To
  67. # submit the change with the review, include 'submit: True' with the
  68. # reviewkey. Reviewkeys appear in the help text for the change
  69. # screen.
  70. reviewkeys:
  71. - key: 'meta 0'
  72. approvals: []
  73. - key: 'meta 1'
  74. approvals:
  75. - category: 'Code-Review'
  76. value: 1
  77. - key: 'meta 2'
  78. approvals:
  79. - category: 'Code-Review'
  80. value: 2
  81. - key: 'meta 3'
  82. approvals:
  83. - category: 'Code-Review'
  84. value: 2
  85. submit: True