You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gitea version (or commit ref): 1.10.0+dev-39-g50d8d171f
Git version:
Operating system:
Docker / MacOS
Database (use [x]):
[ x] PostgreSQL
Description
I'm working on an automatic setup for a larger number of repositories which is greatly supported by the REST API
I can create repositories etc.
I can create teams etc.
I can create organizations etc.
(It might be a good way to support such things via command line client but gitea client seemed to be limited at the moment and the new one tea is not available as a release and if I correctly understand the current state it's not really usable at the moment).
Unfortunately I can't set advanced settings off repositories via REST API like using external issue tracker, external issue tracker URL format, external issue tracker number format etc.
So either it's not possible at the moment or I simply missed something.
The text was updated successfully, but these errors were encountered:
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.
Docker / MacOS
[x]
):Description
I'm working on an automatic setup for a larger number of repositories which is greatly supported by the REST API
(It might be a good way to support such things via command line client but gitea client seemed to be limited at the moment and the new one
tea
is not available as a release and if I correctly understand the current state it's not really usable at the moment).Unfortunately I can't set advanced settings off repositories via REST API like using external issue tracker, external issue tracker URL format, external issue tracker number format etc.
So either it's not possible at the moment or I simply missed something.
The text was updated successfully, but these errors were encountered: