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
Is your feature request related to a problem? Please describe.
Repo metadata is currently set via cli commands.
I always neet to look at the commands again because I do not use these regularely.
Describe the solution you'd like
Some way to set or update the description or other values via the main branch in a configuration-as-code kind of way.
This could be done by creating a .soft-serve file of any format (e.g. json, yaml, ini, ...) or data pulled from a kind of metadata block inside the readme file (like pandoc does)
Values that might be useful to set this way:
project-name
description
is-private
is-hidden
collaborators
This might also be used for settings hooks and similar if security allows that. (maybe by only allowing server preconfigured hooks)
But I am pretty new to soft-serve and git server hooks so I do not know if that is a good/useful idea.
Is your feature request related to a problem? Please describe.
Repo metadata is currently set via cli commands.
I always neet to look at the commands again because I do not use these regularely.
Describe the solution you'd like
Some way to set or update the description or other values via the main branch in a configuration-as-code kind of way.
This could be done by creating a
.soft-serve
file of any format (e.g. json, yaml, ini, ...) or data pulled from a kind of metadata block inside the readme file (like pandoc does)Values that might be useful to set this way:
project-name
description
is-private
is-hidden
collaborators
This might also be used for settings hooks and similar if security allows that. (maybe by only allowing server preconfigured hooks)
But I am pretty new to soft-serve and git server hooks so I do not know if that is a good/useful idea.
Describe alternatives you've considered
see above
Additional context
The text was updated successfully, but these errors were encountered: