Use function setup_commit_message everywhere to avoid duplication of
these lines.
Also, document the side effects of the function in the invocation.
Change-Id: I3b77a232467b536b62b5c61d30705deeb11e725e
The sample config updater had a couple of problems
1) It would steal a different proposal bot review (e.g., if there
was a review for requirements update it would be replaced with a
config update. The fix for this is to fetch reviews for the
topic.
2) The topic was incorrect since it was like
openstack/openstack/keystone/genconf, there's an extra "openstack/".
Change-Id: I6fa5c78d7ea18aecbb96c573be78a42560b3b158
The keystone team updates the sample configuration file in it's
own patch, so to not stomp on other patches.
We've had to update the configuration files manually, but we
should create an automated job. Since it's just running
tox -e genconfig and checking diff output.
Change-Id: I0e294b857d9bbf73e7f9c0d0bdee61648fb999bd