Skip to content

feat: 🎸 add GitHub welcome action to welcome new contributos#1057

Open
trueberryless wants to merge 5 commits intoall-contributors:mainfrom
trueberryless:feature/welcome-pr-bot
Open

feat: 🎸 add GitHub welcome action to welcome new contributos#1057
trueberryless wants to merge 5 commits intoall-contributors:mainfrom
trueberryless:feature/welcome-pr-bot

Conversation

@trueberryless
Copy link
Copy Markdown
Contributor

Description

Add a new welcome bot GitHub action which runs on new merge requests and checks if this is the first interaction of the user with the repository. If so, it will write a lovely welcome message, assuring that the user did everything correctly and that a review can take some time. 🙌

Why?

I think this action makes new contributors feel welcomed!

@netlify
Copy link
Copy Markdown

netlify bot commented Mar 17, 2026

Deploy Preview for all-contributors ready!

Name Link
🔨 Latest commit 3ed657a
🔍 Latest deploy log https://app.netlify.com/projects/all-contributors/deploys/69c8159b5f10b300084653b0
😎 Deploy Preview https://deploy-preview-1057.staging.allcontributors.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Copy Markdown
Member

@JimMadge JimMadge left a comment

Choose a reason for hiding this comment

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

A few questions about the actions, but this looks good to me. I like the idea of having something to welcome and inform new contributors 👍

@trueberryless
Copy link
Copy Markdown
Contributor Author

Actually, I just found out that the actions/first-interaction requires the issue_message parameter alto it shouldn't be (see this issue), so reverted the last commit for now.

Copy link
Copy Markdown
Member

@JimMadge JimMadge left a comment

Choose a reason for hiding this comment

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

Let's remove the checkout step if it isn't needed.

Shame that the upstream project has a bug. Can we use an older version? Or maybe wait for actions/first-interaction#404 to be merged?

@trueberryless
Copy link
Copy Markdown
Contributor Author

Shame that the upstream project has a bug. Can we use an older version? Or maybe wait for actions/first-interaction#404 to be merged?

However you'd like. I kinda doubt that my PR in the upstream action will be merged any time soon, so I wouldn't bet on waiting for it. And I can also confirm that the fork action works, as we have it running in Starlight and also npmx. But I'll leave the decision up to you whether you wanna use the fork in the meantime or rather have no welcome until the official action works 👍

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.

2 participants