Skip to content
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

docs: improved issue templates #3698

Merged
merged 1 commit into from
Feb 8, 2025

Conversation

Andrew15-5
Copy link
Contributor

The "Please add the corresponding labels to the issue." line started the chain reaction (issue OP can't add labels), and now I just overall polished the current templates.

From the docs, the non-YAML templates are considered legacy templates, but the documentation for them is still up. I'm not user if we should switch. But Typst uses them and I didn't have any problems with them.

@Andrew15-5 Andrew15-5 requested a review from a team as a code owner February 5, 2025 20:36
@Andrew15-5
Copy link
Contributor Author

Actually, I requested this for Typst, and I think for Dioxus this also will be helpful. I want to have a separate docs template. This is what I very frequently wanted to use in Typst, but they didn't have it until I asked.

@Andrew15-5
Copy link
Contributor Author

Oh, and with the form style template you can choose the platform from the dropdown menu, and it should be able to automatically add the appropriate labels. Though I haven't tried/seen that. So I guess there is a good reason to switch to them.

Copy link
Member

@jkelleyrtp jkelleyrtp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thank you!

@jkelleyrtp jkelleyrtp merged commit 9b71a33 into DioxusLabs:main Feb 8, 2025
16 of 17 checks passed
@Andrew15-5 Andrew15-5 deleted the improved-issue-templates branch February 8, 2025 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants