Skip to content

drivers: pulse_io: add vendor-neutral timed-edge IO subsystem #89543

drivers: pulse_io: add vendor-neutral timed-edge IO subsystem

drivers: pulse_io: add vendor-neutral timed-edge IO subsystem #89543

name: Greet first time contributor
on:
issues:
types: [opened]
pull_request_target:
types: [opened, closed]
permissions:
contents: read
jobs:
check_for_first_interaction:
runs-on: ubuntu-24.04
if: github.repository == 'zephyrproject-rtos/zephyr'
permissions:
pull-requests: write # to comment on pull requests
issues: write # to comment on issues
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
- uses: zephyrproject-rtos/action-first-interaction@58853996b1ac504b8e0f6964301f369d2bb22e5c # v1.1.1+zephyr.6
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
issue-message: >
Hi @${{github.event.issue.user.login}}! We appreciate you submitting your first issue
for our open-source project. 🌟
Even though I'm a bot, I can assure you that the whole community is genuinely grateful
for your time and effort. 🤖💙
pr-opened-message: >
Hello @${{ github.event.pull_request.user.login }}, and thank you very much for your
first Pull Request (PR) to the Zephyr Project!
All PRs must pass our Continuous Integration (CI) pipeline before merging.
When the pipeline run for your PR completes, you are expected to investigate the
results, fix any errors, and update your PR for a fresh round of review.
Since this is your first contribution, a project community member must manually
approve your CI run (this helps us avoid abuse of our CI system). A bot should assign
some reviewers who can start the run for you soon.
As a heads-up, you will probably have to update your PR to fix CI issues
and address review feedback in order to get it ready for merge.
Some key rules for updating your PR are:
- **do** amend problematic commits on your computer and force push the fixed commits into your PR branch on GitHub
- **don't** push new commits just to fix problems in existing PR commits (amend your commits instead)
- **don't** close your PR and open an updated one unless reviewers specifically request it (force push to your branch instead)
- **do** rebase your PR branch onto our main branch and force push to this PR to resolve merge conflicts
- **don't** merge our main branch into your PR branch to fix merge conflicts
Also, see:
- [Contribution Guidelines](https://docs.zephyrproject.org/latest/contribute/guidelines.html) for details on how contributing to Zephyr works
- [Contributor Expectations](https://docs.zephyrproject.org/latest/contribute/contributor_expectations.html) to learn what our community expects from you
- [Reviewer Expectations](https://docs.zephyrproject.org/latest/contribute/reviewer_expectations.html) to learn what you can expect from community members who review this PR
If you are stuck or need help, you can join us on
[Discord](https://chat.zephyrproject.org/) and ask questions; many community members
try to help new contributors there 😊. Try to pick a Discord channel that is
associated with the technical details of your request. If you're not sure,
use the #general channel.
pr-merged-message: >
Hi @${{ github.event.pull_request.user.login }}!
Congratulations on getting your very first Zephyr pull request merged 🎉🥳. This is a
fantastic achievement, and we're thrilled to have you as part of our community!
Now that your first PR is merged, CI will run automatically on subsequent PRs that you
send from the same GitHub account.
To celebrate this milestone and showcase your contribution, we'd love to award you the
Zephyr Technical Contributor badge. If you're interested, please claim your badge by
filling out this form: [Claim Your Zephyr Badge](https://forms.gle/oCw9iAPLhUsHTapc8).
Thank you for your valuable input, and we look forward to seeing more of your
contributions in the future! 🪁