Adding Issue and Pull Request templates #86
Conversation
|
No spelling errors! 🎉 |
|
No broken url errors! 🎉 |
|
👀 Quick preview of website here * * note not all html features will be properly displayed in the "quick preview" but it will give you a rough idea. Updated at 2024-11-07 with changes from the latest commit d5ef425 |
|
@cansavvy added steps to the filing automatic issues workflow yml since it overlaps the starting-course workflow from the main OTTR template. This should be ready for your review |
|
Related main OTTR template PR this one is emulating: jhudsl/OTTR_Template#759 |
There was a problem hiding this comment.
Thanks for adding this @kweav !!
I do wonder if this many issue templates will be a little overwhelming for users but I lean toward thinking its probably less overwhelming than a blank issue page so probably better. Let's try it out and we can always change it later.
We can merge this and then no need for stacked you can start a new PR. Thanks again! |
Oh sorry, I didn't update the description. This commit was the work that I was going to do next in a stacked PR if I didn't get to it before your review: 79abeb8 |
Adding Issue and Pull Request templates mirroring the main OTTR template.
Specifically was doing this because we added issue and pr templates for adding courses to OTTR syncs and we wanted to do this for websites too.
Used
wgetto get the raw.mdfiles for each issue and PR template and edited them to reflect websites instead of courses.Still need to add a new website cleanup workflow because several of the templates assign @cansavvy to handle the issue or PR and we don't want that happening in other people's websites. @cansavvy do you want me to try to do this in a stacked PR and have you review it?