emilyshaffer@xxxxxxxxxx writes:
> + /*
> + * Doesn't look like there is a list of all possible hooks; so below is
> + * a transcription of `git help hook`.
That's "git help hooks", if I tried my reproduction correctly. A
straight-forward (in the sense of "what we want in the outcome is
quite clear" and not in the sense of "anybody can design and
implement it with a single 30-line patch") follow-up we can make
after this series lands is to rethink how Documentation/githooks.txt
is maintained and the list we have here is synchronized with it.
The design could me just the matter of running "grep" of some sort,
with appropriate markups that are no-op to AsciiDoctor/AsciiDoc
added to the documentation source, to produce this list.
> + */
> + const char *hooks = "applypatch-msg,"
> + "pre-applypatch,"
> + "post-applypatch,"
> + "pre-commit,"
> + "pre-merge-commit,"
> + "prepare-commit-msg,"
> + "commit-msg,"
> + "post-commit,"
> + "pre-rebase,"
> + "post-checkout,"
> + "post-merge,"
> + "pre-push,"
> + "pre-receive,"
> + "update,"
> + "post-receive,"
> + "post-update,"
> + "push-to-checkout,"
> + "pre-auto-gc,"
> + "post-rewrite,"
> + "sendemail-validate,"
> + "fsmonitor-watchman,"
> + "p4-pre-submit,"
> + "post-index-changex";
> + struct string_list hooks_list = STRING_LIST_INIT_DUP;
> + struct string_list_item *iter = NULL;
> +
> +
> + if (nongit) {
> + strbuf_addstr(hook_info,
> + "not run from a git repository - no hooks to show\n");
> + return;
> + }
> +
> + string_list_split(&hooks_list, hooks, ',', -1);
> +
> + for_each_string_list_item(iter, &hooks_list) {
> + if (find_hook(iter->string)) {
> + strbuf_addstr(hook_info, iter->string);
> + strbuf_complete_line(hook_info);
> + }
> + }
> +}
> +
> static const char * const bugreport_usage[] = {
> N_("git bugreport [-o|--output <file>]"),
> NULL
> @@ -193,6 +243,9 @@ int cmd_main(int argc, const char **argv)
> get_header(&buffer, "Safelisted Config Info");
> get_safelisted_config(&buffer);
>
> + get_header(&buffer, "Configured Hooks");
Phrase nit. There may be many people who just enabled hooks without
configuring, so "Enabled Hooks" may be more appropriate. We do not
have to inspect what is in the hook to determine if it is enabled,
but we do need to if we want to tell if a hook is "configured".
> + get_populated_hooks(&buffer, nongit_ok);
> +
> report = fopen_for_writing(report_path.buf);
> strbuf_write(&buffer, report);
> fclose(report);
