Skip to content

CI: compile with "baseline" Bun versions #1238

CI: compile with "baseline" Bun versions

CI: compile with "baseline" Bun versions #1238

name: GitHub First Interaction
on:
pull_request_target:
types:
- opened
jobs:
first-interaction:
name: Welcome First Time Contributors
runs-on: ubuntu-latest
steps:
- uses: actions/first-interaction@1c4688942c71f71d4f5502a26ea67c331730fa4d # v3.1.0
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
# TODO(cemmer): https://github.com/actions/first-interaction/issues/365
issue_message: |
## :wave: Welcome
Thank you for your first pull request, @${{ github.event.pull_request.head.user.login }}!
_Comment generated by the [${{ github.workflow }}](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}/attempts/${{ github.run_attempt }}) workflow._
pr_message: |
## :wave: Welcome
Thank you for your first pull request, @${{ github.event.pull_request.head.user.login }}! If you haven't yet, please familiarize yourself with Igir's [contribution guidelines](https://github.com/emmercm/igir/blob/main/.github/CONTRIBUTING.md).
Some GitHub Actions CI workflows may not automatically run for you due to GitHub's [security best practices](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#controlling-changes-from-forks-to-workflows-in-public-repositories), so a maintainer may need to manually approve the workflows to run. As a result, it is important to make sure tests pass locally before submitting a pull request to help ensure a fast review. Thank you!
_Comment generated by the [${{ github.workflow }}](https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}/attempts/${{ github.run_attempt }}) workflow._