Add an option in the config file to set a person as the assignee for issues or PRs?

[kweav]

Wondering about adding an option in the config file with a github username that we can use in workflows or issue templates to set an assignee when an Issue or PR is created such that users are more likely to see these quickly? Want an easily editable way (like a config file option) so that users we set aren't propagated to all users of the template.

Does it have to have a default or is it possible to make it so it grabs a user if one is specified and has current template behavior otherwise?

Discussion on this in PR #22

[KatherineCox]

One way we've handled things when we need OTTR_Template to behave differently than repos based on the template is to either delete or swap out the file with starting-course.yml.

For example, this line

OTTR_Template/.github/workflows/starting-course.yml

Line 33 in b1bc2db

mv .github/course_README_template.md README.md

replaces the README when a new course is created.

[kweav]

Yes, I've utilized the method you're referring to a few times -- but thanks for mentioning it! While it could definitely work for making sure downstream courses are't by default assigning us to issues, I think the config approach has the strength of assigning someone to a course/repo they have ownership of pretty easliy.