-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Issue Config #20956
Implement Issue Config #20956
Conversation
should the path be |
@lunny I have now changed the paths |
@lunny Any more suggestions or should I add documentation, so this can be merged? |
Hi, sorry to be late to reply. Maybe you could add some documentation and tests? And maybe @wolfogre could also have a review because he contributed some related PRs. |
The documentation has now been added, but i don't know, how to write tests for this. |
|
||
### Possible Options | ||
|
||
| Key | Description | Type | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think Default
is also a good idea for this table.
I had now done a bit of code refactoring:
|
Need @delvh approval. |
Ping @delvh |
Happened to see this PR ..... maybe the maintainer team need some mechanisms to handle the "pending reviews"? Should I help to call the TOC (again)? |
Need @delvh 's review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, sorry for the late reply, my TODO list is way too long already.
Furthermore, I'm still not quite a fan of using a boolean
where I think a string is more fitting.
However, I can at least accept this PR assuming everyone knows that this is probably not the best option for a long-term solution.
This comment was marked as off-topic.
This comment was marked as off-topic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've now tested the functionality.
A few closing remarks:
- I think the API route can be either under
repo
or underissue
. I can certainly see why it's currently under repo. GitHub doesn't offer this API at the moment, so I'm fine with both - I am not a fan of having
_
in URLs but seeing that other URLs also have the_
already, I'll allow it - There should be a divider between the issue templates and the contact links, however, this can be postponed for a later PR:
I'm still not a fan of using a boolean
for that struct, but other than that I don't see anything holding this PR back.
I personally prefer it when it has no divider and everything looks the same (except for the buttons) in the box.
I still think, it's better to add a extra setting. A string that is a boolean is confusing and can cause problems with the API. |
🎺 🤖 |
* upstream/main: Refactor internal API for git commands, use meaningful messages instead of "Internal Server Error" (go-gitea#23687) Add CSS rules for basic colored labels (go-gitea#23774) Add meilisearch support (go-gitea#23136) Add missing translation for `actions.runners.reset_registration_token_success` (go-gitea#23732) [skip ci] Updated translations via Crowdin Implement Issue Config (go-gitea#20956) Set repository link based on the url in package.json for npm packages (go-gitea#20379) Add API to manage issue dependencies (go-gitea#17935) Add creation time in tag list page (go-gitea#23693) Make minio package support legacy MD5 checksum (go-gitea#23768) Yarden Shoham has a new email address (go-gitea#23767) fix br display for packages curls (go-gitea#23737)
Closes #20955
This PR adds the possibility to disable blank Issues, when the Repo has templates. This can be done by creating the file
.gitea/issue_config.yaml
with the contentblank_issues_enabled
in the Repo.I have no experience in Go, so this code might not be perfect, but it is working. If anybody knows how to do that better, just say it. It is also missing documentation at the moment.