Ability to customise the default GIT REPO template #13114

New Issue

GiteaMirror · 2025-11-02T10:31:33-06:00

GiteaMirror commented

2025-11-02 10:31:33 -06:00

Originally created by @StrikerNZL on GitHub (Jun 7, 2024).

Feature Description

One thing I am finding annoying and I honestly don't know if it's even feasible..

We use Gitea internally for DevOps and are currently adding a Python script as a hook in the post-receive.d hook directory due to webhook with Jenkins not working and not triggering builds on a commit.. basically what I think would be a good idea is

either thu the git repo template to add a hook file so that every repo gets a copy of a file.. as determined by the administrator.

in our case, it would allow for the CI/CD workaround to work by automatically adding our Python script into the post-receive.d directory, the same could be said for other files like licensing agreements or whatever the business policy or development workflow was.

Screenshots

No response

Originally created by @StrikerNZL on GitHub (Jun 7, 2024). ### Feature Description One thing I am finding annoying and I honestly don't know if it's even feasible.. We use Gitea internally for DevOps and are currently adding a Python script as a hook in the post-receive.d hook directory due to webhook with Jenkins not working and not triggering builds on a commit.. basically what I think would be a good idea is either thu the git repo template to add a hook file so that every repo gets a copy of a file.. as determined by the administrator. in our case, it would allow for the CI/CD workaround to work by automatically adding our Python script into the post-receive.d directory, the same could be said for other files like licensing agreements or whatever the business policy or development workflow was. ### Screenshots _No response_

GiteaMirror added the type/proposal issue/needs-feedback labels 2025-11-02 10:31:33 -06:00

GiteaMirror closed this issue

2025-11-02 10:31:33 -06:00

GiteaMirror commented

2025-11-02 10:31:34 -06:00

@delvh commented on GitHub (Jun 7, 2024):

It is never a good idea to add files forcefully to every repo
Why not use Gitea Actions? That should already achieve what you want. Sure, you still need to copy this file for every repo (unless you create a template repo), but I think that's a small price to pay for not damaging the entire security model
Template repos exist

@delvh commented on GitHub (Jun 7, 2024): 1. It is never a good idea to add files forcefully to every repo 2. Why not use Gitea Actions? That should already achieve what you want. Sure, you still need to copy this file for every repo (unless you create a template repo), but I think that's a small price to pay for not damaging the entire security model 3. [Template repos exist](https://docs.gitea.com/usage/template-repositories)

GiteaMirror commented

2025-11-02 10:31:34 -06:00

@GiteaBot commented on GitHub (Jul 7, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jul 7, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13114