Skip to content

Don't add an asignee in the package issue template - #308

Merged
dstansby merged 5 commits into
mainfrom
no-default-asignee
Feb 19, 2024
Merged

Don't add an asignee in the package issue template#308
dstansby merged 5 commits into
mainfrom
no-default-asignee

Conversation

@dstansby

Copy link
Copy Markdown
Contributor

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 github_user does not indicate value can be an organisation #305 by changing the github_user field to stand for either a user or organisation.

@paddyroddy paddyroddy left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we sure it will work when assignees isn't present altogether? Should we be doing

assignees:

@dstansby
dstansby marked this pull request as draft February 19, 2024 10:51
@dstansby

Copy link
Copy Markdown
Contributor Author

I've rebase on to the schema validation PR, and removing assignee altogether passes the validation.

@paddyroddy
paddyroddy self-requested a review February 19, 2024 11:24
@dstansby

Copy link
Copy Markdown
Contributor Author

Whoever merges please squash merge!

@dstansby
dstansby marked this pull request as ready for review February 19, 2024 13:25
@dstansby
dstansby merged commit 9a37774 into main Feb 19, 2024
@dstansby
dstansby deleted the no-default-asignee branch February 19, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

github_user does not indicate value can be an organisation

2 participants