retrieve publicly available emails as well

[mac2000]

This is an very first baby step going to solve #1532 feature request

Technically all we are doing here is adding one more field to GraphQL query and map it to response, aka:

query getAllMembers($org:String!,$after:String) {
  organization(login:$org) {
    membersWithRole(first:100,after:$after) {
      nodes {
        id
        login
        email # <- added
      }
    }
  }
}

This should not brake anything because we are not touching any existing fields, only adding new one, the idea was to introduce this first and as a next step try to figure out how can we rewrite code in a such way so it will retrieve all users if no inputs given, but to me it seems better to do it step by step, otherwise it may become to many changes to review

Here is how sample output will look like:

To be fair I'm not sure if passing such data in different lists is a good idea but cannot touch it without braking something else so at first iteration we may keep it simple

---

Behavior

After the change?

• Email field added to response

Other information

• @kfcampbell I'm not sure if you asked about something like this, but I did tried to do my best

---

Additional info

Pull request checklist

• [+] Tests for the changes have been added (for bug fixes / features)
• [+] Docs have been reviewed and added / updated if needed (for bug fixes / features)
• [+] Added the appropriate label for the given change

Does this introduce a breaking change?

• [+] No

Pull request type

Type: Feature

---

[kfcampbell]

@mac2000 thanks! Could you provide appropriate documentation for this field in the website/docs/d/users.html.markdown file so our docs stay up-to-date?

[nickfloyd]

Thanks, @mac2000 for this change! ❤️