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

Automatically respond to new user actions #13

Open
3 of 6 tasks
RayStick opened this issue Apr 19, 2024 · 0 comments
Open
3 of 6 tasks

Automatically respond to new user actions #13

RayStick opened this issue Apr 19, 2024 · 0 comments
Assignees
Labels
Internal Changes affect the internal API. It doesn't increase the version, but produces a changelog

Comments

@RayStick
Copy link
Member

RayStick commented Apr 19, 2024

In other GitHub projects I've been involved in, they provide welcome messages in the form of comments when

  1. someone opens their first Issue
  2. someone opens their first PR
  3. someone merges their first PR

The welcome message is a nice friendly touch but can also provide an opportunity for them to be automatically reminded of where to look for relevant resources and what checklist to follow. This is done via a .github/config.yml file using this bot - https://github.com/apps/welcome

Steps to take:

  • Implement the 3 welcome/congrats messages in this test repo
  • Discuss with physiopy team what to write in these 3 welcome/congrats messages (assume they will be the same for every repo in physiopy, but confirm that with team)
  • Implement the 3 welcome/congrats messages in all physiopy repos
  • Use a similar approach to address this PR which wants to produce a checklist for the main reviewer of a PR
@RayStick RayStick added the Internal Changes affect the internal API. It doesn't increase the version, but produces a changelog label Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Changes affect the internal API. It doesn't increase the version, but produces a changelog
Projects
Status: In Progress
Development

No branches or pull requests

1 participant