Uh oh!
There was an error while loading. Please reload this page.
Add a workflow for welcoming first-time contributors - #55
Conversation
ahoppen
left a comment
There was a problem hiding this comment.
I don’t think this workflow design will work because GitHub Actions will be disabled for first-time contributors and thus the action will not trigger on the `pull_request_target
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I am reading through this and getting the impression that the limitation applies to workflow runs — regardless of whether they depend on actions. But the note says that |
8d31115 to
66b4ebbCompare66b4ebb to
084eab0Compareahoppen
commented
Nov 4, 2024
I’m sorry. I meant to remove that comment after I realized that you’re using |
ahoppen
left a comment
There was a problem hiding this comment.
Looks good to me but I would like @shahmishal to review this as well because it’s a new workflow.
AnthonyLatsis
commented
Nov 5, 2024
Sure, I’d like that too! Thanks for reviewing, Alex. |
| pull_request_message: | ||
| description: > | ||
| The Markdown message to comment when a contributor creates their first | ||
| pull request. | ||
| type: string | ||
| required: false | ||
| issue_message: | ||
| description: > | ||
| The Markdown message to comment when a contributor creates their first | ||
| issue. | ||
| type: string | ||
| required: false |
There was a problem hiding this comment.
Can we provide a default message for both? Would avoid every repo to define its own custom message. Maybe even going one step further do we want each repo to customise this really? If so how do you expect them to customise this?
The text for the message itself that Contributor Experience Workgroup discussed: |
parispittman
commented
Mar 6, 2026
ship it :) |
I tested the workflow in my swift fork, albeit without the first-time contributor condition. Once this lands, we can use the contributor experience repo to further test it against pull requests from forks.