pr and issue templates + typecheck ci python #138
Inorishio
No Assignees
AramJonghu
AramJonghu
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: zach/z-bar-qt#138
Reference in New Issue
Block a user
Description
Add issue/PR templates using Gitea YAML forms for structured bug reports, feature requests, and pull requests. This PR is an example of how the PR template would look like. Sadly; showing how issue templates look like is tedious to check until it is on a default branch (
main).Also add basedpyright type checking to Python CI workflow as I noticed we were not using these. Consider adding config file to cover warnings/errors of our choice. Currently, the typecheck fails.
Related Issue
Closes #135
Type of Change
Tested
Breaking Changes
None.
Checklist
WIP: init(new branch): New branchto WIP: pr templates9df351b544tof75fef3f55pr templatesto pr and issue templates + typecheck ci pythonLooks good to me. Only thing I have to say is maybe we should make an input field for non-systemd users to write their init system. It's not very useful right now since currently it is indeed just
if not systemd; thenbut it could be useful later down the line if specific, non-systemd features are added.Yea; I thought it would be better to have the user manually fill their init system. It would be quite the noise to add most of the init systems available. For now though, most init system issues would be down to taking into account a user is not using uwsm.
Absolutely agreed, I didn't mean making a dropdown option for each init system. I just meant adding a non-required text input where the user can write their init system.