Add the ability to disable Wiki & Issues from API #164

New Issue

GiteaMirror · 2025-11-02T03:11:33-06:00

GiteaMirror commented

2025-11-02 03:11:33 -06:00

Originally created by @deanpcmad on GitHub (Dec 26, 2016).

I've recently moved to Gitea from GitLab. I wrote a script to extract the GitLab backup, create repos using the Gitea API and then push the contents of those repos.

For a number of my projects I want to use an external issue tracker so it would be nice to be able to disable or set the external issue tracker URL and URL format from the API on creation and when updating a project.

Thanks for your hard work on Gitea so far, I'm really liking it 😄

Originally created by @deanpcmad on GitHub (Dec 26, 2016). I've recently moved to Gitea from GitLab. I wrote a script to extract the GitLab backup, create repos using the Gitea API and then push the contents of those repos. For a number of my projects I want to use an external issue tracker so it would be nice to be able to disable or set the external issue tracker URL and URL format from the API on creation and when updating a project. Thanks for your hard work on Gitea so far, I'm really liking it 😄

GiteaMirror added the type/feature issue/confirmed type/enhancement modifies/api labels 2025-11-02 03:11:33 -06:00

GiteaMirror closed this issue

2025-11-02 03:11:33 -06:00

GiteaMirror commented

2025-11-02 03:11:34 -06:00

@lunny commented on GitHub (Jan 25, 2017):

Is there a github API to do this?

@lunny commented on GitHub (Jan 25, 2017): Is there a github API to do this?

GiteaMirror commented

2025-11-02 03:11:34 -06:00

@bkcsoft commented on GitHub (Jan 29, 2017):

@lunny Yes. https://developer.github.com/v3/repos/#edit

PATCH /repos/:owner/:repo
{
  has_wiki: false,
  has_issues: false
}

@bkcsoft commented on GitHub (Jan 29, 2017): @lunny Yes. https://developer.github.com/v3/repos/#edit ``` PATCH /repos/:owner/:repo { has_wiki: false, has_issues: false } ```

GiteaMirror commented

2025-11-02 03:11:35 -06:00

@stale[bot] commented on GitHub (Jan 30, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 30, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:11:35 -06:00

@adelowo commented on GitHub (Jan 30, 2019):

Bummer

@adelowo commented on GitHub (Jan 30, 2019): Bummer

GiteaMirror commented

2025-11-02 03:11:35 -06:00

@stale[bot] commented on GitHub (Mar 31, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 31, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:11:36 -06:00

@davidsvantesson commented on GitHub (Nov 24, 2019):

This issue have been implemented.

@davidsvantesson commented on GitHub (Nov 24, 2019): This issue have been implemented.

GiteaMirror referenced this issue

2025-11-02 11:41:04 -06:00

[PR #164] [MERGED] fixed bug #151 finally #15196

Sign in to join this conversation.