Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/ISSUE_TEMPLATE/01-github-request---onboarding.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,10 @@ body:
- type: textarea
id: users
attributes:
label: User List (case sensitive!) - Please also include in ticket title
description: Which user(s) are you requesting access for? Note GitHub usernames are case-sensitive, so please enter in the correct capitalization.
label: User List (case sensitive!) - Please also include usernames in ticket title
description: Who are you requesting access for, and what are their GH usernames and emails? GH usernames are case-sensitive, so please enter in the correct capitalization.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we indicate a way for them to PM us the email addresses, in case they don't want them fully visible on the interwebs?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, emails aren't required for all onboarding requests, right? Only 2U onboards people to their CLA through this form. People asking to onboard a user to say, openedx-triage we don't need email addresses. I wonder if we should have 2U follow the process everyone else follows to get them attached to their entity CLA.

Copy link
Member Author

Choose a reason for hiding this comment

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

Per discussion in standup, we'll close this PR and work towards 2U using the same process as other firms with entity CLAs.

placeholder: |
* Full Name Here, @username_here
* Full Name Here, @username_here, their-email-address@example.com
* ...
validations:
required: true
Expand Down