behaviorbot / welcome Goto Github PK

Using probots app

Would be cool if one could also have the option of tagging a PR w/a config defined label

Royalty

Test

hi there,

first off, thanks for making this app! I love the idea of welcoming new contributors.

That said, the app doesn't appear to work on private repositories. I tested it on this one (would be happy to invite you if you can't repro).

https://github.com/annthurium/testing-oss-automations/

I made an alternate GitHub account, invited that account to collaborate on the repository, and tried opening a pull request and an issue with the alt account. Neither resulted in a comment from the bot. And I did create a config file at .github/config.yml and copied in the boilerplate config example.

It DOES work on this repo, which is public.
annthurium/affirmations#4

If this is expected behavior, it might be good to document it on the app page so users aren't caught off guard.

Thanks!

Every time I merge a PR on interactive-examples repository, firstPRMergeComment is displayed. Those messages were sent in PR 2254, PR 2271(comment was deleted) and in PR 2277. All of those pull requests were created by users who have contributed to this repo for the first time. config.yml seems to be ok.

👋 Please add the probot-apptopic. See probot/probot.github.io#40 for details.

electron/electron#13969 (comment)

Previously, electron/electron#12631

https://sentry.io/probot/welcome/issues/323440102/

Error: Empty value for parameter 'body': undefined

It looks like this happens when a .github/config.yml exists, but doesn't have the property that the plugins expects.

Probot is currently on v7.2.0, while several behavior bot apps are lagging behind. I'd appreciate some help getting them all updated!

This will require the following:

1. updating the Probot entry in each package.json.
2. Running npm install (If you don't already have node and npm installed, you'll need to do so here).
3. Running npm test and fixing any errors that may arise from that. I think the main issue will be renaming robot to app.
4. Get all tests back to passing;
5. Open a PR and ping me for review!

Here are the apps that need updating:

• sentiment-bot
• request-info
• welcome (Welcome depends on these 3 sub-apps which will need to be updated first:
  • first-pr-merge
  • new-pr-welcome
  • new-issue-welcome
• update-docs

All behaviorbot repos should be updated as such.

cc probot/probot#235

test

I am using that bot on organization and I want to avoid to add a config file in all the repo.
It will be helpful to have a way to set an unique file for all the repo of an organization that shares the settings.

Hello and thank you for your work.

I'm using Welcome to notify the issue author that one of the maintainers will look into it as soon as possible. I'm calling the team from within the message:

Thanks for your contribution! One of the @WrocTypeScript/organisers will go back to you as soon as possible.

Unfortunately, without access to Organization members this cannot work. The recommended solution is to request read permission in your application settings.

What do you thnik? Would that make sense?

hello hello it me just testing latest deploy of welcome bot

As this bot exists, it will welcome users to the repository. Many orgs (like us) have a lot of small repositories and would only like to welcome users to the org once.

Now that this can use the org level .github repository, I'd like to have a key in there like WelcomeBotOrgWide: true to instruct the plugins to look for issues & PRs across the whole org and not just the repository.

I suggest upgrading Probot to the latest version.