Skip to content
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

first ideas for a github notification tool #72

Closed
wants to merge 2 commits into from

Conversation

ChristianKuehnel
Copy link
Collaborator

First draft for "Gerald", a user-customizable notification tool for GitHub, similar to what
Herald does
for Phabricator.

> *GeraldBot commented on Aug 27th:*
>
> notifying @Elaine1234, @Gao1234

Copy link
Collaborator

Choose a reason for hiding this comment

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

This is pretty good already, but I fear that the first email will look like:

@gerald[bot] requested your review on: #1234

With nothing more, right?

@ChristianKuehnel
Copy link
Collaborator Author

ChristianKuehnel commented Oct 4, 2021 via email

@joker-eph
Copy link
Collaborator

Actually, since we have a similar tool in TensorFlow. I checked and when the bot is mentioning me on Pull-request GitHub sends me two email: first the one I didn't get on creation of the pull request with all the info, and then the mention from the bot. So it seems that GitHub is smart enough to adjust its notification here!

@ChristianKuehnel
Copy link
Collaborator Author

Based on the discussion on the llvm-dev mailing list:
We can't store Personally Identifiable Information (PII) in our repos for privacy reasons. While we can keep public information like assigning labels to issues in the repo, we need to move all personal information somewhere private.

To store user data privately, we need some database and users need to authenticate. And that means we need to build a UI for managing the notifications. All of that make the project larger and requires more effort...

@joker-eph
Copy link
Collaborator

Are we considering a GitHub username as PII? Your Gerald proposal only needs to mention this and no email right?
See what the Rust folks do: https://github.com/rust-lang/highfive/blob/master/highfive/configs/rust-lang/rust.json#L14-L15

@joker-eph
Copy link
Collaborator

One more reference: CIRCT folks tried https://github.com/marketplace/actions/use-herald-action (but it was buggy so they stopped)

I was pointed out to https://github.com/marketplace/actions/auto-request-review (but without any particular experience with it)

@ChristianKuehnel
Copy link
Collaborator Author

Are we considering a GitHub username as PII?
I'm not a privacy expert, but I would say this meets GitHub's definition

@joker-eph
Copy link
Collaborator

From the mailing list, this may also fit the bill! https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners

(Note that, coming back to PII, it means that GitHub's own solution is to put usernames in a file in the repo...)

@tstellar
Copy link
Collaborator

I did a proof of concept notifier a while back. You can take a look at it here: https://github.com/llvm/temp-issue-tester

@joker-eph
Copy link
Collaborator

joker-eph commented Oct 15, 2021

For more related work:

TensorFlow bot auto-assign pull-requests based on a config like this: https://github.com/tensorflow/tensorflow/blob/master/.github/bot_config.yml

This is a custom bot I believe, it also has a config to ping when a pull-request is inactive for a while (and later close it): https://github.com/tensorflow/tensorflow/blob/master/.github/stale.yml#L22-L38

@joker-eph
Copy link
Collaborator

Another one mentioned in the RFC thread: https://github.com/gagoar/use-herald-action

@ChristianKuehnel ChristianKuehnel marked this pull request as ready for review November 4, 2021 08:31
@ChristianKuehnel
Copy link
Collaborator Author

Another one mentioned in the RFC thread: https://github.com/gagoar/use-herald-action

They are also storing the user names in config files in the repo. I'm not sure if that is what we want.

@ChristianKuehnel
Copy link
Collaborator Author

closing as we already have another solution in place

@ChristianKuehnel ChristianKuehnel deleted the gerald_design branch March 1, 2022 17:01
@joker-eph
Copy link
Collaborator

Are you referring to the team management for GH Issues? I don't think it is a direct replacement to Herald for pull-request.

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.

3 participants