-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create GitHub Issue Templates #5
Comments
I think that's kinda just it tbh. I'd think of a new name than 'typo' since I think it's a bit unclear for new people that a typo is anything from literal typo to formatting improvement (e.g. tagging, using a better |
That's what I meant by Book Request, but yeah, should word that better.
Also I should note as I think I didn't say this before, I don't want to use Discord for tracking issues anymore. Its bothersome, relies on a Discord bot, and requires a Discord account to "properly" report stuff. |
I think "Missing Paizo content" is a fine enough name. I want Paizo in the issue title, at least. Is simply "conversion error" clear enough? idk 🤔
Definitely—IssueCrawler is a bit... finnicky. It's just for homebrew requests imo, based on what we see in mothersite's #brew-requests channel. I don't want that in here at all. Though we don't really need a bot for that; could just be a dedicated channel where users type posts following a certain template. |
Where are we storing homebrew anyway in the end? If its going to be yet another repo that is a submodule of this one, then making it a GitHub Issue template won't be that of a problem anyway. If it's going to be here, I suppose there's more hesitancy, but GitHub has good filtering capabilities so its minimal hassle to filter out homebrew requests. |
I wanted it to be here for nice centralisation reasons. It's just that the |
Worth making a background homebrew just so we have something to test with. "Artificer" perhaps? |
Done now! |
Something for me to do. Current ideas for templates include:
Feel free to comment any more that should be added.
The text was updated successfully, but these errors were encountered: