-
Notifications
You must be signed in to change notification settings - Fork 60k
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
Need to add more email details #34756
Comments
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
@nguyenalex836 Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
Hi @nguyenalex836, Thank you for your quick response and for triaging this issue! I appreciate your efforts in addressing the concerns regarding the email invitation process for collaborators. I believe including an example email template in the documentation would greatly enhance clarity and security for users. It would help them understand what information is shared when inviting collaborators and alleviate concerns about potential data leakage. suggested template for the invitation email that could be added to the documentation: Subject: Invitation to collaborate on the repository <REPOSITORY_NAME> Hello, You have been invited by <INVITER_USERNAME> to collaborate on the repository "<REPOSITORY_NAME>" on GitHub. To accept the invitation, click the link below: Best regards, In addition to the template, it might be useful to mention that the inviter's email address is not shared with the invitee, which could provide an extra layer of reassurance for users. Thank you for considering this suggestion, and I look forward to any further feedback! |
@phionex2 Thank you for the suggestion! Our writers will review your template once they've had a chance to look into this issue 💛 |
@nguyenalex836 Thank you for promptly responding to this. Looking forward to updates. @phionex2 Thank you for contributing a new suggestion. Are you interested in networking further with other engineers like myself? Below I have shared the present email template used for repo invitations, which should be added to the doc page for inviting collaborators. The relevant doc page shared in the first comment should be updated everytime the email template changes to reflect the changes so repository owners can fully understand security risks. An additional change that would be valuable is the option to remove usernames from the emails sent out, as that can be loaded after the invitation url is navigated to.
Looking forward to communicating further with you all. I have also opened a community thread that can be found here: |
I appreciate the opportunity to network further with engineers like yourself, and I’m always eager to connect and collaborate! @llvee Thank you for sharing the email template. I agree that updating the documentation with the current email format will help users understand security risks better. I also support the idea of removing usernames from the email for added privacy. |
Hello, I'm not sure what changes you're proposing exactly—could you let us know which article specifically you mean? You've put https://github.com/github/docs/tree/main/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github in the original issue, but this is a series of articles rather than one specifically. Also: our team doesn't control what text is sent when a user is invited to collaborate on a repository and I'm afraid I'm not seeing what help a template would be. One of the mechanisms for inviting users is via their email address, but if this is done via a username (as the documentation states is one of the options) then there's no reason the inviter should see the invitee's email address as part of that process. I'll defer back to @nguyenalex836 and I'll circle back via him if there's something I'm missing. Thank you! |
Thank you for continuing to contribute. Let's network further sometime soon. You're welcome. Hello again, thank you for continuing to contribute. I shared some skills improvements as well. I tried to tag you, was unable to do so due maybe to lack of your account being in the skills org specifically. Thank you for taking the time to review, consider this more & for joining this discussion as well. I studied the first post I made again. Since @phionex2 was able to understand, find the relevant page it seems that the link was likely replaced somehow without my permission. I have updated the link to the correct link. The functionality, email template should be the same regardless of whether a user is invited via username or email. I haven't done extensive testing to confirm that. Having the option to change the invite template would be nice, however lots of work for the dev team & would likely add additional security risks. Adding the current invite to repo template to the docs is a must in order for engineers to fully understand the security risks associated with inviting others to repositories. |
Thank you for your reply—
I'm afraid I still don't see how this would be helpful for users. The text is subject to change but simply states something along the lines of " I simply don't see enough reason to action this particular request so I'm going to close this issue. Thank you for your interest in the GitHub Docs! Please feel free to look at our issues marked |
Adding the template will help users properly understand the security risks associated with inviting other users or third parties to the code repositories by being able to see the specific user information or data that is being shared with invitees. This also will help Github avoid future lawsuits, reputational damage likely due to security, privacy & negligance issues associated with not sharing more specific information as lack of neccesary information in the documentation also increases the rates of data breaches, data leaks, service, user & business damages. This shouldn't be closed as resolved until the documentation is updated. Is this explanation more clear? |
I am going through all of the skills courses more soon. I can also maybe share some feedback about improving Skills further. If you're interested in my response to Subatoi, check my prev response before this one. |
👋 Hello GH users & team members, thank you all for considering these changes.
Today I decided to explore collaborating, communicating with other users more.
While studying the documentation for inviting others to repositories I considered the security implications of the invite feature specifically.
While thinking more about security implications I noticed that there was not enough information in the docs page to fully understand or know them.
Code of Conduct
What article on docs.github.com is affected?
https://github.com/github/docs/blob/main/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
What part(s) of the article would you like to see updated?
The article mentions sending emails, falls short when it comes to sharing an exact template or message used to invite others. This is important for security as it's currently impossible to ascertain whether inviting another person to a repository shares the login email for the account with them or not.
Additional information
This affects anyone who uses the invitation docs to understand the feature better. Adding more information about exact emails sent can help prevent lots of unauthorised account accesses, data leaking.
🚀 How Docs/Skills can be:
🧔 Not Me:
Please:
💡 View my other Github issues, community discussions (updating with links soon.)
💡 Follow my account
💡 Fork repositories
💡 Star repositories
💡 Comment here for further networking
💡 Reach out if you'd like to support me on Buymeacoffee, Ko-fi & similar channels
What are your thoughts on the above?
Did you notice any other improvements that can be made to documentation or skills?
The text was updated successfully, but these errors were encountered: