Implement Default Webhooks

[aunger]

Partially implement #770. (This is only webhooks, not git hooks.)

• Add "Default Webhooks" page in site admin UI.
• Persist to the existing webhooks table, but store with RepoID=0 and OrgID=0.
• Add a few handlers and templates, but mostly modify the existing ones to serve double-duty. I should point out that installations that have customized the webhooks templates (probably uncommon) will need to edit them to accomodate a slight change in the semantics of .BaseLink.
• Upon repo creation, copy the set of default webhooks into the new repo.
• A repo owner may delete or edit these webhooks if he doesn't like the defaults.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@cac9e6e). Click here to learn what that means.
The diff coverage is 22.76%.

@@            Coverage Diff            @@
##             master    #4299   +/-   ##
=========================================
  Coverage          ?   38.86%           
=========================================
  Files             ?      365           
  Lines             ?    51341           
  Branches          ?        0           
=========================================
  Hits              ?    19953           
  Misses            ?    28516           
  Partials          ?     2872

Impacted Files	Coverage Δ
routers/admin/hooks.go	0% <0%> (ø)
models/repo.go	47.36% <0%> (ø)
routers/org/setting.go	0% <0%> (ø)
routers/routes/routes.go	83.44% <100%> (ø)
models/webhook.go	63.18% <21.56%> (ø)
routers/repo/webhook.go	1.73% <3.33%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cac9e6e...32b3e68. Read the comment docs.

[aunger]

It's been a while. Should I merge master into this branch now to make review easier, or is it best to wait?

[aunger]

I'm confused about why drone failed. Is it a drone bug, or something I did wrong?

[techknowlogick]

@aunger let me re-trigger drone.

[techknowlogick]

@aunger drone is all good now. I suggest asking in the #develop channel on discord for a maintainer to review this PR

[aunger]

Thanks for your help, @techknowlogick, but I've tried Discord a few times and don't get much response. Would you mind doing the review yourself?

@lunny, would you review this too? I see you hearted it. It's been languishing for two months now.

Thanks.

[lunny]

@aunger I will review and test it. but that maybe spend my some time.

[lunny]

LGTM

[aunger]

@ethantkoenig Mind reviewing this PR? This would turn one of your ufw customizations into an admin setting. https://github.com/unfoldingWord-dev/gogs/blob/a2489be2c7ab4d3d20838135bb1d538c2eb5f40c/models/repo.go#L1363

[ethantkoenig]

@aunger I won't be able to, sorry.

[lafriks]

Can default webhooks be stored to new table, so that this functionality could be later extended more easily?

[aunger]

@lafriks Someone could certainly implement it that way. This PR's KISS approach is better in some ways though, because the plumbing is more easily shared (don't need an abstraction of a webhook if they are all the same) and it requires less attention to table schemas. What future extensions do you have in mind?

[lafriks]

@aunger I would like to have ability to have forced webhooks for all repositories, updating webhooks for repositories when changing default webhook, ability to select/deselect from default webhooks in repository settings etc

[aunger]

@lafriks Great ideas. Site-wide hooks are more flexible. I was weighing most of that before I implemented this, but I didn't get any feedback (#770 (comment)), so I decided to go simple ("agile"?) with this implementation, because it's all my organization needs right now (and because it's what #770 explicitly asked for).

[aunger]

@lafriks I won't tackle site-wide hooks right now. If you're going to code it up now, that's awesome. If not, I hope you consider merging this implementation in the meantime. Thanks.