-
Notifications
You must be signed in to change notification settings - Fork 2
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
github_user
does not indicate value can be an organisation
#305
Labels
Comments
This comment was marked as resolved.
This comment was marked as resolved.
I would suggest removing the assignee from the Github issue templates? Especially for collaborative projects, I don't think it makes much sense to have a single issue assignee, and from my experience a lot of the time I work on projects that don't have a single person assigned to every issue so it would be nice not to have this as default on. |
dstansby
added a commit
that referenced
this issue
Feb 19, 2024
The motivation behind this is: 1. In my experience it's rare for a single person to be assigned every issue in a repository. Much more common are no-one is assigned by default, multiple people (e.g. core developers) are assigned by default, or a group is assigned by default. 2. Not having a GitHub user in the issue template makes it much easier to fix #305 by changing the `github_user` field to stand for either a user *or* organisation.
This is not fixed via #308 although that PR solves my comment, above. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I didn't realise that the intent of the
github_user
variable was to be the username or organisation where the git repository is remotely located. So when I ran the cookiecutter I put in my username, then had to change it all to the org I was actually using.I think this is best solved by solving #296.
The text was updated successfully, but these errors were encountered: