GitHub No Reply Email Address for Privacy & Avoiding SPAM

Open
#22 3 comments 22 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
28/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github

Research direction

Start with the linked GitHub article about commit email addresses and the repository's quick-start development guide. Determine whether this issue calls for documenting GitHub no-reply addresses for Git commits; done should be a clear decision and an updated guide, but no file or test is named in the issue.

Written by the indexing model from the issue text.

Description

discuss enhancement question starter

While researching how to fix the issue of git commits not being authored #21 & #12 I stumbled up on:
https://help.github.com/articles/about-commit-email-addresses/

If you'd like to keep your personal email address private, you can use a GitHub-provided no-reply email address as your commit email address. To use your noreply email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your noreply address for web-based Git operations, set your commit email address on GitHub and choose to Keep my email address private.

If you haven't enabled email address privacy, you can choose which verified email address to author changes with when you edit, delete, or create files on GitHub. If you enabled email address privacy, then the commit author email address cannot be changed and is username@users.noreply.github.com by default.

This might be a good idea for avoiding Spam and Phishing ... 🤔

Dominant language
No language data
Stars
84
Forks
22
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/dev-setup

All issues in dwyl/dev-setup

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.